Re: [gentoo-user] ARGH I uninstalled python

[Dale]

Alan McKinnon wrote:
> On Sunday 24 May 2009 11:28:30 Neil Bothwick wrote:
>
>> On Sun, 24 May 2009 11:07:13 +0200, Alan McKinnon wrote:
>>
>>>> Portage is not in system, only the virtual. That can be
>>>> satisfied by Paludis, which does not need Python.
>>>>
>>> Lucky for you, I know your sense of humour by now :-)
>>>
>>> Doesn't help portage users though, and portage is still the default
>>> package manager on Gentoo. I don't see that changing any time soon, if
>>> ever.
>>>
>>> Besides, unless you do it manually, you need portage to install
>>> paludis, right? Without python, you don't get paludis.
>>>
>>> Either way, it's a bug. portage supports inheriting multiple parent
>>> profiles. One approach would be to add a new collection of profiles in
>>> addition to the existing base/, default/ and targets/ - called say
>>> pkgmgr.
>>>
>> Is it really a bug? Postage is the default for the virtual and it depends
>> on python, so there is no need for python itself to be in @system. This
>> doesn't cause any problems except the one Dale mentions, which is that
>> FEATURES=buildsyspkg does not build a package for python. man make.conf
>> describes this option as "Build binary packages for just packages in the
>> system set. Which is accurate but maybe not the desired behaviour. The
>> option should really by to build packages for packages in @system and
>> their dependencies. Put another way, build all the packages necessary to
>> run "emerge -eK @system".
>>
>> I'd suggest filing an enhancement request on b.g.o.
>>
>
> Using the "this is very unexpected behaviour" definition of bug, I certainly
> do call it a bug. All three of the following commands, produce the same end
> result (a b0rked system), but are treated very differently. I my mind, delete
> warnings should be handled the same as installs, by taking the entire dep tree
> into account:
>
> alan@nazgul ~ $ sudo emerge -avC python
> Password:
>
>
>>>> These are the packages that would be unmerged:
>>>>
>
>  dev-lang/python
>     selected: 2.5.4-r2 2.6.2
>    protected: none
>      omitted: none
>
>
>>>> 'Selected' packages are slated for removal.
>>>> 'Protected' and 'omitted' packages will not be removed.
>>>>
>
> Would you like to unmerge these packages? [Yes/No] n
>
> Quitting.
>
> alan@nazgul ~ $ sudo emerge -avC portage
>
>
>>>> These are the packages that would be unmerged:
>>>>
>  * Not unmerging package sys-apps/portage-2.2_rc33 since there is no valid
>  * reason for portage to unmerge itself.
>
>
>>>> No packages selected for removal by unmerge
>>>>
> alan@nazgul ~ $ sudo emerge -avC gcc
>
>
>>>> These are the packages that would be unmerged:
>>>>
>
>
> !!! 'sys-devel/gcc' is part of your system profile.
> !!! Unmerging it may be damaging to your system.
>
>
>  sys-devel/gcc
>     selected: 4.3.3-r2
>    protected: none
>      omitted: none
>
>
>>>> 'Selected' packages are slated for removal.
>>>> 'Protected' and 'omitted' packages will not be removed.
>>>>
>
> Would you like to unmerge these packages? [Yes/No] n
>
> Quitting.
>
> I'll file a feature request
>
>

+1 

All I know is this:

1:  If I accidentally remove python, portage will not say a word as far
as warning me this is bad.  This is what got the OP into this.  If he
had this warning, he may not have done this.  Prevention is the best way
but even that doesn't work.

2:  Once #1 happens, your pretty much screwed because you don't even
have a binary backup even tho it is set in make.conf to have one.  That
was the reason I put that setting in make.conf but someone chose to
screw with my setting and its meaning.  I guess now buildpkg is my only
option.  It's the only way to insure I can recover if I make a boo boo.

3:  Portage is the package manager for Gentoo.  As Alan said, it always
has been and most likely always will.  I'm not against having other
package managers but if they are going to start messing up my settings,
then I plan to gripe at least a little.  If they are not going to
support buildsyspkg then it needs to be announced and removed.  False
security is worse than none at all. 

My opinion on how this SHOULD work.  If I do a emerge -e system, every
package it builds should have a binary saved for back up.  It doesn't
matter if it is a dependency on something else or not, it should be
built and stored.  That was the purpose of that.

Dale is going to go change this to buildpkg and run emerge -e system. 
Let's see if that even works or not.

Thanks Alan.

Dale

:-)  :-)