On Sun, Aug 2, 2009 at 17:07, Keith Dart<[email protected]> wrote:
>> Just installing it doesn't break portage. But using it does! :)
>

Exactly. When I ran this (and then went for breakfast and coffee):
/usr/bin/eix-sync
/usr/bin/emerge --update --newuse --deep --keep-going --with-bdeps
y/usr/bin/emerge --update --newuse --deep --keep-going --with-bdeps y
world
/usr/bin/emerge --depclean
/usr/bin/revdep-rebuild -C -P

I ended up with Python 3.1 and no 2.x which made a horrible mess. I
ended up having to manually download and install Python 2.x into /opt
and pointing /usr/bin/python to it to get things functional enough
again to re-emerge the 2.6 release. So, ok, maybe it doesn't 'replace'
it, but something sure as hell removed it, which is clearly the wrong
behavior since emerge depends on it. Please enlighten me where I went
wrong as I'd rather not have such surprises in the morn. :)
-- 
Douglas J Hunley, RHCT
[email protected] : http://douglasjhunley.com : Twitter: @hunleyd

Obsessively opposed to the typical.

Reply via email to