On Fri, 2005-07-01 at 15:59 -0700, Drake Wyrm wrote: > Mike Frysinger <[EMAIL PROTECTED]> wrote: > > On Friday 01 July 2005 12:25 pm, Brian D. Harring wrote: > > > Currently, we pretty much leave out the big dogs of build depends from > > > ebuilds- basically we rely on the profile to require a suitable > > > toolchain. Couple of issues with this though- > > > > so what you're proposing is that we add binutils/gcc/glibc to every package > > that compiles something > > Can you compile without binutils/gcc/glibc? No? Then you need it. > > > make to every package that uses make, > > Again, if you depend on make, then DEPEND on make. > > > sed/grep/bash/coreutils to every package which runs configure > > That's quite an interesting case. Yes, those should be in DEPEND, but it > might be prudent to create an appropriate shortcut instead of explicitly > adding each of those. >
This is all well and dandy, but try to add coreutils as a dependency of itself, or gcc of itself, or sed ... or grep ... etc, and then try to do a stage1 install (probably stage2/3 as well, but I never do those, so rather wont comment). The point that Mike and I make, is that portage cannot handle this (and probably wont be able to in future without a _lot_ of black magic), and this is why we need the system profile which have just the right amount of DEPEND magic to make it work, and then everything else depends automagically on the system profile (and everything in it). Making the adding of system packages to non system packages really redundant. Sure it might be fixable, but the only way I see how, is to have a complete system profile (with all the dependencies that are currently lacking), and then # emerge --oneshot --nodeps $(cat /some/path/system-profile) But this gets to the verge of being too static, having the effect that some optional dependencies for the system profile cannot be used. (There are probably other ways, but this is the first that I could think of, and more as an example ...) Thanks, -- Martin Schlemmer Gentoo Linux Developer, Desktop/System Team Developer Cape Town, South Africa
signature.asc
Description: This is a digitally signed message part
