On Wed, Aug 15, 2012 at 7:07 AM, Fabian Groffen <grob...@gentoo.org> wrote: > On 15-08-2012 12:58:32 +0200, Michał Górny wrote: >> Rich Freeman <ri...@gentoo.org> wrote: >> > 2. Things like Prefix rely on the system not installing local copies >> > of libraries in the core system it needs to link to. Careful use of >> > package.provided in profiles might address this. > > Huh? Not sure I understand this, but it suggests something which isn't > true for Prefix to me.
Do you want every other package in the tree depending on glibc, and therefore trying to pull it in on a prefix system? (For those unaware, prefix depends on a non-Gentoo glibc for the system call interface.) There are probably a few ways you could do it, but if you got rid of the implicit @system dependency then you'd need to handle situations where @system is something non-traditional and ebuilds are likely to do it wrong. Agree with mgorny's suggestion that anything required by PMS could be pulled in by the package manager, perhaps in an EAPI-dependent fashion. Oh, @system has another use I didn't mention - getting rid of some chicken-and-egg issues during the initial install. That can be addressed by providing pre-built stage1/2/3s, having package sets and scripts for their building, and so on. Maybe make world a world.d directory with Gentoo providing a starter file and users modifying their own addition, but being free to remove items and depcleaning them. Or provide a syntax for world to remove packages pulled in by a distro-provided world, etc. Many elements of this would benefit from public comment obviously should we choose to go along this road. Rich
