* Johan Vromans <[EMAIL PROTECTED]> [2006-08-04 17:25]: > Adrian Howard <[EMAIL PROTECTED]> writes: > > On 4 Aug 2006, at 14:04, Johan Vromans wrote: > >> For this to function properly, the 'build_requires' modules > >> (and their respecitve dependencies!) should all be > >> downloaded and installed in a temporary location (e.g., > >> blib) and not be installed permanently. > > > > I don't think that's the necessary conclusion. Personally I > > prefer build requirements to be installed permanently - so I > > don't have to build them repeatedly when multiple modules > > require the same build requirements. > > Apparently we differ in opinion.
How? 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`. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>
