Mike Edenfield wrote:
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
Just picking a random post here. The devs know this. It has been
pointed out on -dev and on b.g.o. as well. They won't do anything to
correct this. It just seems to me that portage shouldn't break itself.
Since there are other package managers, they should not be able to break
themselves either. I think maybe it should be the package manager
itself that prevents this. That way it fixes it for everyone. I'm just
not sure this is doable.
The biggest point is, the devs know but are not interested in fixing
it. Their response is to shut up and get over it, not in those words
but still.
Dale
:-) :-)
