Jason Stubbs schreef: > On Friday 27 May 2005 01:07, Holly Bostick wrote: > >>Jason Stubbs schreef: >> >>>On Thursday 26 May 2005 23:36, Neil Bothwick wrote: >>> >>>>On Thu, 26 May 2005 16:24:28 +0200, Holly Bostick wrote: >>>> >>>>>Now of course I know that Portage depends on Python, and I certainly >>>>>don't want to mess up Portage, so how do I get rid of this version of >>>>>Python (or how do I recover if there's no way to get rid of it without >>>>>breaking anything)? >>>> >>>>Portage depends on Python 2.3, unmerging that and leaving 2.4 could break >>>>things, the other way round shouldn't. >>> >>>Portage works with >=python-2.2. Unmerging either 2.3 or 2.4 should not >>>cause any troubles with portage at all as the libraries and scripts live >>>outside the python directories. >> >>OK, that's reassuring-- but what still concerns me a bit is that when I >>request to unmerge a specific version of Python, Portage: >> >>1) does not confirm (before getting hysterical) the version I am unmerging; > > > --pretend or --ask as per usual.
For a system package, this does not seem to work: mutable root # emerge -Cav =dev-lang/python-2.4.1 ________________________________________________________________________________ cfg-update 1.7.1 : Building checksum index... (takes a few seconds) done! ________________________________________________________________________________ >>> These are the packages that I would unmerge: !!! Trying to unmerge package(s) in system profile. 'dev-lang/python' !!! This could be damaging to your system. >>> Waiting 10 seconds before starting... >>> (Control-C to abort)... Press Ctrl-C to Stop in: 10 9 8 7 6 Exiting on signal 2 As you see, I did use -a, and maybe it was going to ask me in 4 more seconds (as I do get the correct "These are the packages I *would* unmerge"), but the very fact that there is an immediate countdown (which does not happen when you are "asking" first) is scary enough that I would never let the countdown finish just to see if Portage really *was* going to wait for me to confirm before proceeding. At least not without doing the quickpackages first. It's just unexpectedly contradictory behaviour. > > >>2) gets all hysterical as if I am uninstalling a mission-critical >>application -- which it "knows" I am not, because the original ebuild >>was not only installed to a new slot, but also gave me a statement that >>my original Python was being retained for compatibility, etc, etc. > > > $ grep python /usr/portage/profiles/base/packages > *dev-lang/python > > Portage checks the package you are about to unmerge against the list of > "system" packages and then warns if it matches. Slots aren't taken into > account at all but probably should be. That would likely reduce the "mixed-message factor" I seem to be sensing here. Holly -- gentoo-user@gentoo.org mailing list
