| 1 |
On Tuesday 03 May 2005 09:10, Chris Gianelloni wrote: |
| 2 |
> I think an easier solution would be a portage rescue set of profiles. |
| 3 |
> These would be minimal profiles not designed for actual use, but only |
| 4 |
> for performing a portage update for those people that lag too far |
| 5 |
> behind. The idea would be a very tiny profile, per arch, that is not |
| 6 |
> cascaded. |
| 7 |
|
| 8 |
Perhaps another solution would be to create a system with archives of the |
| 9 |
profiles and packages necessary to do an upgrade from an old portage and |
| 10 |
profile to a new portage and profile, seeing as portage has circular |
| 11 |
effective dependencies on at least the tree and python, perhaps other stuff |
| 12 |
as well. This could be some sort of script which downloads the archive, then |
| 13 |
upgrades, one major shift at a time. |
| 14 |
|
| 15 |
Once said system is in place, notices could be put in the deprecated files |
| 16 |
(and of course the homepage) to that effect, and the old profiles removed |
| 17 |
from the main tree after a while. |
| 18 |
|
| 19 |
Just a thought. |
| 20 |
|
| 21 |
--electronerd |
Archives