"A. Pagaltzis" <[EMAIL PROTECTED]> writes: > If the packager installs the build dependencies in order to build > a package, what’s the difference? The package won’t contain > build-time dependencies any more than it will contain runtime > dependencies, and since build-time dependencies are listed > separately from runtime dependencies it’s easy to create a > package that lists only the latter as its dependencies. > > I don’t see why any of this requires installing to `blib`.
Because the next module that you build will not let you know that it requires modules that you have already installed on your build system as part of the build-time dependencies of (yet another) module. So it increases the probability that modules will be forgotten to be included in the install kit. Oh yes, there's always a test install that will (hopefully) complain. I didn't say it's wrong, I just said it increases the maintenance load. -- Johan
