-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 7 Jul 2001, Stefan van der Eijk wrote:
>>And how about a package 'essential-devel' which depends on gcc, make and
>>all the other devel stuff included in a Mandrake default install. This
>>package wouldn't contain any files, it would just act as a convenient
>>collection of dependencies, so that if essential-devel is installed you
>>know the basic stuff is there.
>Then you'll need to install one package that Provides: essential-devel.
Yes. It would probably be installed as part of a standard Mandrake
setup - unless MandrakeSoft decide to drop gcc and make from the
standard install.
>I'm not sure if this is the way to go, it's got an "artificial" feeling...
I think it is the least messy option. I don't know if there is
precedent for this sort of thing though.
>The result of the "BR march" should be that no matter which package
>you're going to rebuild, if you install the BuildRequires, a (hopefully)
>good package is going to come out.
Agreed. The question is, do we want to list *every single package* as a
BuildRequires line? Surely we can't have a hundred lines listing
dependencies on bash, textutils, gzip, and so on. So where do you
draw the line, and having done so is there an easy way to make sure that
these prerequisites are installed? (Nobody could uninstall bash, but
it's possible to imagine a basic Mandrake install without, say,
glibc-devel.)
- --
Ed Avis <[EMAIL PROTECTED]>
Finger for PGP key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7SDNHIMp73jhGogoRAqHiAJwIW9bJLQKpRIAbIuOSHFx9ks6ppwCfaxN4
iiseknjD0aVj9nNeh29W6wY=
=QD8K
-----END PGP SIGNATURE-----
