| 1 |
On Monday, August 1 at 12:41 (+0200), Joost Roeleveld said: |
| 2 |
|
| 3 |
> On Sunday, July 31, 2011 11:02:22 AM Florian Philipp wrote: |
| 4 |
> > @system used to contain portage. It doesn't by default, anymore. If |
| 5 |
> you |
| 6 |
> > do `emerge -pv --depclean`, portage should try to remove itself. |
| 7 |
> Just |
| 8 |
> > add it to @world by doing `emerge --noreplace portage` |
| 9 |
> |
| 10 |
> It doesn't try this on my system |
| 11 |
|
| 12 |
Yeah, I don't think that statement was entirely accurate. Deplean |
| 13 |
"normally" will not try to remove portage, because it satisfies the |
| 14 |
virtual/package-manager requirement, which is in @system. |
| 15 |
|
| 16 |
If, however, you have portage and another package satisfying |
| 17 |
virtual/package-manager installed, and the other package was in your |
| 18 |
world file, but portage wasn't then depclean *would* remove portage. |
| 19 |
This is the recent behavior change, which is why some people were |
| 20 |
surprised suddenly when nano or less or |
| 21 |
insert_your_favorite_virtual_here was suddenly wanting to get unmerged |
| 22 |
by --depclean. |
Archives