Re: Keeping information on the build system
On Fri, 12 Oct 2001, Yann Dirson wrote:
> OTOH, we could take the approach of listing in build-essential the
> tools that are most commonly used so that everyone does not have to
> list them, and allow maintainers to specify a Build-Unused list of
> build-essential packages not in use.
That wouldn't make sense.
Build-Depends was created so that a package could be built easily. Not so
that you'd know what software is used to accomplish the build.
You know, build-essential packages an extension to essential packages. If
you want build-essential packages to be installed, you need packages with
"Essential: yes" to be installed too. That includes base-files, which is
rarely used when doing a build. But would you uninstall it "because you
don't need it for this build"? I doubt that.
Build-essential was created so that people wouldn't start doing
build-depends on obvious packages. Not because you have to build-depend on
IIRC, policy explicitely states you don't have to build-depend on
build-essential, but I'm not sure and too lazy to find out ;-)
wouter dot verhelst at advalvas dot be
"Human knowledge belongs to the world"
-- From the movie "Antitrust"
rm -rf /bin/laden