| 1 |
Stephen P. Becker wrote: |
| 2 |
> Portage should have been warning such users about using a deprecated |
| 3 |
> profile for some time now. So, they should have updated to a new |
| 4 |
> profile by now. Surely most people have synced portage sometime recently |
| 5 |
> and done an emerge -uD world. If somebody is using a portage snapshot |
| 6 |
> from two years ago, they have more problems than a deprecated profile. |
| 7 |
|
| 8 |
What is bad about doing *only* `emerge --sync` and security updates? |
| 9 |
This is not my case so it's quite possible that no such users exist (so |
| 10 |
the gentoo-dev ml isn't probably the best place to ask if they exist, |
| 11 |
btw), but if you do something that will prevent *everyone* who is so |
| 12 |
"late with upgrades" from continuing, you'll introduce (IMHO dangerous) |
| 13 |
precedence about backward compatibility. |
| 14 |
|
| 15 |
So I'm just asking if those users (even if nobody like that exist) have |
| 16 |
an ability to upgrade or at least to carry on with their security |
| 17 |
upgrades (which could of course require update of sys-apps/portage, this |
| 18 |
is perfectly correct). |
| 19 |
|
| 20 |
Good thing is that `emerge --sync` produces warning about using |
| 21 |
deprecated profile, so it will probably catch the attention. |
| 22 |
|
| 23 |
> You do realize that for the most part, gentoo versions don't mean very |
| 24 |
> much, right? A gentoo install is as current as the portage tree, no |
| 25 |
> matter what installer was used. |
| 26 |
|
| 27 |
Sure. |
| 28 |
|
| 29 |
TIA, |
| 30 |
-jkt |
| 31 |
|
| 32 |
-- |
| 33 |
cd /local/pub && more beer > /dev/mouth |
Archives