Re: Bug#70269: automatic build fails for potato
- To: debian-devel@lists.debian.org
- Subject: Re: Bug#70269: automatic build fails for potato
- From: Steve Greenland <stevegr@debian.org>
- Date: Wed, 30 Aug 2000 11:26:51 -0500
- Message-id: <[🔎] 20000830112651.C694@molehole.dhis.org>
- Mail-followup-to: debian-devel@lists.debian.org
- Reply-to: Steve Greenland <stevegr@debian.org>
- In-reply-to: <4.3.2.7.0.20000829170030.00b83b90@armstrong.cse.buffalo.edu>; from bmbuck@14850.com on Tue, Aug 29, 2000 at 05:05:02PM -0400
- References: <20000829004006.A24173@silly.cloud.net.au> <20000828182155.D6955@gaia.iki.fi> <20000829082216.A25268@silly.cloud.net.au> <20000829080203.I6955@gaia.iki.fi> <20000829092919.A5724@murphy.nl> <20000829120823.A11158@gaia.iki.fi> <20000829205408.A26589@silly.cloud.net.au> <87lmxgvwcj.fsf@glaurung.green-gryphon.com> <20000829155239.B13399@molehole.dhis.org> <4.3.2.7.0.20000829170030.00b83b90@armstrong.cse.buffalo.edu>
On 29-Aug-00, 16:05 (CDT), Buddha Buck <bmbuck@14850.com> 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.
Repeating myself: listing a tool as build-essential does not mean that
packages are required to use it, just that packages my assume that the
tool is present.
Steve
--
Steve Greenland <stevegr@debian.org>
(Please do not CC me on mail sent to this list; I subscribe to and read
every list I post to.)
Reply to: