On 2/4/2010 10:43 AM, Neil Bothwick wrote:
On Thu, 4 Feb 2010 16:14:25 +0200, Alan McKinnon wrote:
How about giving the same warning when unmerging a dependency of
@system as you do when unmerging a package directly in there. Either
way, you risk breaking the system.
Aren't all deps of packages in @system themselves already in @system?
No, otherwise portage would complain if you tried to unmerge python.
Anyway, deps are USE-dependent. Try USE="X" emerge @system on a headless
server to see jut how much @system can pull in.
Portage isn't in @system, either. "virtual/portage" is, but paludis
also provides that. Python isn't a dependency of any other system
package (except "file", but that's only enabled by the USE flag).
It appears that portage's refusal to unmerge itself is hard-coded into
portage; that reinforces my belief that portage should be responsible
for refusing to unmerge it's own dependencies.
--Mike
