On 20 July 2013 21:21, Dicebot <[email protected]> wrote: > It is nothing of real importance but question is, what harm does > explicit versioning do?
It has no direct or immediate harmful consequence, but it is a packaging convention here. Most of our uses for versioning dependencies come during testing (when the package along with its dependencies is in that repo) and rebuilds (when a whole bunch of packages are moved wholesale with their proper dependencies). Otherwise, you may find core packages to have these things in order to be compatible (or rather, not be compatible) with certain other things. We simply do not care about legacy upstream dependency information because we provide the latest, always. If you have a strong reason (and not just copying verbatim upstream's minimum requirements), go ahead and keep things versioned. -- GPG/PGP ID: C0711BF1
