On 20000830T112651-0500, Steve Greenland wrote:
> On 29-Aug-00, 16:05 (CDT), Buddha Buck <[EMAIL PROTECTED]> wrote:
> > Would it make sense to make policy something like "All official Debian
> > auto-build machines will have installed this set of build packages: gcc,
> > ..., and debhelper. Debian packages are not required to specify build
> > dependencies on these packages."
>
> That's pretty much the definition (or at least the *use*) of
> Build-Essential: packages that may be assumed to be present, so that
> they need not be listed in Build-Depends.
It's not the definition. One of the explicit design goals for the current
setup was that policy should not need to mention specific packages.
The definition is the following:
It is not be necessary to explicitly specify build-time relationships
on a minimal set of packages that are always needed to compile, link
and put in a Debian package a standard "Hello World!" program written
in C or C++. The required packages are called _build-essential_, and
an informational list can be found in
`/usr/share/doc/build-essential/list' (which is contained in the
`build-essential' package).
(Debian Policy v. 3.2.1.0, section 2.4.2.)
--
%%% Antti-Juhani Kaijanaho % [EMAIL PROTECTED] % http://www.iki.fi/gaia/ %%%
Hypertekstivisionääri Ted Nelson luennoi Jyväskylässä 29.-31.8.
Lisätietoja saa minulta.
