Remember the definition of build-essential: + <p> + It will 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 <em/build-essential/, and an + informational list will be published separately from this + document. + </p> +
On Wed, Oct 27, 1999 at 03:50:06AM -0700, Seth R Arnold wrote: [ What's build-essential?] > Joel Klecker: > > libc-dev Yes: > > gcc Definitely. > > g++ yes. > > libstdc++-dev yes. > > patch Only if something else requires it. (dpkg-source?) > > make Yes. > > dpkg-dev Yes. > > binutils Yes. > > bison No. > autoconf ? No. > bin86 ? Do you need this to compile a Hello World? > ldso ? Do you need this to compile a Hello World? > supporting stuff.... > tar ? Only as a dependency. > cpio ? Only as a dependency. > gzip ? Only as a dependency. > bzip2 ? Only as a dependency. > find ? What needs this? > perl ? What needs this? > less likely, but still possible... > curses ? No. > groff/man ? No. > wish ? No. > python ? No. > jdk ? No. Remember, this list is supposed to be MINIMAL. BTW, what do you people think of the metapackage idea (see the new Policy draft thread)? -- %%% Antti-Juhani Kaijanaho % [EMAIL PROTECTED] % http://www.iki.fi/gaia/ %%% "" (John Cage)
