> In general, options are problematic because while people compiling > from source can set them, they are not really options with respect to > the bulk build. I agree. Which is why my intention was to make the suggestion I made in order to stir up a discussion to find the optimal solution. > So if some kind of web server is a soft run-time dependency, then I > think it makes sense to just not include it as a dependency at all. Indeed. As long as not required for building, I'd strongly suggest to remove all those dependencies, be that to a web-server, or to a programming-language meant to somehow run in/behind a web-server (php, ruby-on-rails, etc). Though with languages, build-dependencies -are- more likely, so these should be included in a way that web-servers are not pulled into the build unsolicited, and may even end up as a dependency when installing the packages. - Volkmar -- http://www.dimensionv.de/ http://tech.nifelheim.info/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - OpenPGP Fingerprint: E03D 33DB B409 2E99 C2DA 7D64 145F 0A76 D252 7078 Key: http://www.dimensionv.de/pgp (+ all public key-servers) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Attachment:
pgpEk5YUPDvE8.pgp
Description: PGP signature