Ow Mun Heng schreef: > On Thu, 2005-05-26 at 18:07 +0200, 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)? > > >>Yes, and I'll be taking that, too. So I should quickpkg 2.3? and >>Portage? Fair enough. > > > > Just for your info, I went down this path like 2 weeks ago when I wanted > something new (i can remember what was it but I reckon it was either > gdekslets or some other app) and I just unmasked 2.4 and 2.3 stayed > back. > > Of course I was surprised to still see 2.3 there so I promptly unmerge > it. Did I see issues? You Bet! Epylog didn't work and so didn't > gdekslets. > > The solution was to re-emerge both of these (revdep-rebuild didn't help > at all) and then everything works. > > That's my experience. >
Thanks for the tip-- in the case that I want to emerge the newest gDesktlets in order to try that spiffy new RSS tickerbar and get off of KDE finally (I really like having a ticker and specifically a scrolling bar, and Knewsticker doesn't so much like running under other DEs), and so wind up with the same situation again, I'll keep it in mind. In any case, I did quickpkg python-2.3.5 and portage, but it was not necessary to use the backups; the unmerge of Python 2.4.1 went fine and all I had to do was re-emerge pysol and java-config. No other applications were disturbed at all. Thanks, Holly -- gentoo-user@gentoo.org mailing list
