On Wed, Oct 27, 1999 at 03:17:52PM +0100, Julian Gilbey wrote: > Firstly, that if we are now demanding build-time dependencies, we are > asking maintainers to do a *lot* of work. (This took me about 2 > hours, maybe a little bit more.) We ought to think of a better way of > performing this task if we want maintainers to take it seriously.
No need to get it absolutely right at first try. We can develop this dependency net over time. > Finally, a small point. It may be worth stating that if a package is > required to satisfy an (install-time) dependency of a listed > dependency, then it does not need to be listed itself. Although, > having said this, I think this is obvious. I don't think it is a good idea. Mixing them up is flawed. Installing a package is quite different from compiling, and we want to minimize build dependencies (for example, maybe I don't need perl to compile something, but only to run it). It will only make things harder, because now we have to figure out which of the install deps are also build deps and which not. We would suddenly find ourselve on the other side of the problem, and not win much. Thanks, Marcus -- `Rhubarb is no Egyptian god.' Debian http://www.debian.org Check Key server Marcus Brinkmann GNU http://www.gnu.org for public PGP Key [EMAIL PROTECTED], [EMAIL PROTECTED] PGP Key ID 36E7CD09 http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ [EMAIL PROTECTED]