SEO

After successfully emerging python 2.4, and running python-updater (which
re-emerged lots of packages) what do I do with the old python 2.3 which
was left in place? I can plainly see some orphan files from applications
in site-packages.

Can I safely unmerged python-2.3? Should I remove the /usr/lib/python-2.3
directory after unmerging? Should I leave everything alone?

Lastly, today, a rev to 2.4 came out, 2.4.2. Do I need to run
python-updater again? Or is that only for minor version bumps (i.e. 2,3 to
2.4) or for sub-versions too?

TIA

Peter <peter@localhost.com> wrote:
>
> Can I safely unmerged python-2.3?

For questions like this ask "emerge -Dep world".
You might want to use a script to compare this list with
the list of actually installed packages, e.g.
the "world" script from
http://www.mathematik.uni-wuerzburg.de/~vaeth/gentoo

> Should I remove the /usr/lib/python-2.3 directory after unmerging?

Yes. It should be pretty empty afterwards anyway (or contains only
files which do not belong to any package).

On Thu, 13 Oct 2005 13:36:41 +0000, Martin Vaeth wrote:

> Peter <peter@localhost.com> wrote:
>>
>> Can I safely unmerged python-2.3?
>
> For questions like this ask "emerge -Dep world".
> You might want to use a script to compare this list with
> the list of actually installed packages, e.g.
> the "world" script from
> http://www.mathematik.uni-wuerzburg.de/~vaeth/gentoo
>
>> Should I remove the /usr/lib/python-2.3 directory after unmerging?
>
> Yes. It should be pretty empty afterwards anyway (or contains only
> files which do not belong to any package).

emerge -Dep showed everything with python 2.4.2 at the top. It gave no
clue about python 2.3 and any stray dependencies though.

/usr/lib/python-2.3 is not very empty at all. python-updater did nothing
when upgrading 2.4.1 to 2.4.2 since it looks only at minor versions, i.e.
2.3. I had run it and it rebuilt around 32 packages.

I did emerge -Cp python-2.3.5-r2 and received a stern warning.

mars peter # emerge -Cp python-2.3.5-r2

>>> 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.


dev-lang/python
selected: 2.3.5-r2
protected: none
omitted: 2.4.2

python 2.3 is only around 34mb so maybe I'll just keep it around unless
someone has a compelling reason to nuke it. Only thing left in
site-packages was stuff for svn, which was also installed in python 2.4.
Probably a fault in the ebuild that stopped it from being removed.

Running peter@mars ~ $ sudo equery d python
[ Searching for packages depending on python... ]
app-arch/rpm-4.2
app-editors/vim-6.3.084
app-editors/gvim-6.3.084
app-portage/gentoolkit-0.2.0-r2
app-text/gnome-doc-utils-0.2.1
dev-java/java-config-1.2.11
dev-lang/python-2.4.2
dev-lang/swig-1.3.21
dev-lang/python-2.3.5-r2

showed python 2.3.5-r2 depending on the current 2.4.2 version!

Thoughts?

Maybe I'll just stand pat.

Peter <peter@localhost.com> wrote:
>
> emerge -Dep showed everything with python 2.4.2 at the top. It gave no
> clue about python 2.3 and any stray dependencies though.

Then you can savely remove it (if your world file is up-to-date).

> I did emerge -Cp python-2.3.5-r2 and received a stern warning.
[...]
>
> !!! Trying to unmerge package(s) in system profile. 'dev-lang/python'
> !!! This could be damaging to your system.

This shouldn't hurt you. Of course, you will be in trouble if e.g.
python 2.4.2 turns out to be so buggy that it is not possible to
start portage with it - but this is rather unlikely (it only reminds
you to convince yourself before that portage still works with the
new python).

> Only thing left in
> site-packages was stuff for svn, which was also installed in python 2.4.
> Probably a fault in the ebuild that stopped it from being removed.

Either that, or these are files which are created after installation
and therefore not contained in the file list of the svn package.

> Running peter@mars ~ $ sudo equery d python
> [...]
> showed python 2.3.5-r2 depending on the current 2.4.2 version!
>
> Thoughts?

I don't know what this equery output means, but such a dependency
does certainly not exist, because otherwise "emerge -Dep world"
would have been forced to list python-2.3.5-r2.