| 1 |
On 09/20/2011 08:19 AM, Zac Medico wrote: |
| 2 |
> On 09/19/2011 03:14 PM, Alex Alexander wrote: |
| 3 |
>> My idea is simple. When incompatible changes have to be introduced to the |
| 4 |
>> tree, push a new version of portage that includes support for all the new |
| 5 |
>> features we want to provide. |
| 6 |
>> |
| 7 |
>> Then, freeze the tree and clone it into a revbumped rsync module, i.e. |
| 8 |
>> |
| 9 |
>> SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage-r1" |
| 10 |
> |
| 11 |
> It's a waste to provide the old copies via rsync. A similar alternative |
| 12 |
> that would solve that is to have a file in the tree that maps older |
| 13 |
> EAPIs to snapshots. That way, after a person syncs and finds that the |
| 14 |
> tree's EAPI is not supported, their package manager can easily locate |
| 15 |
> and download a tree snapshot (from any gentoo mirror) which is supported |
| 16 |
> by the current package manager. |
| 17 |
|
| 18 |
Also, note that these snapshots really only need to contain the subset |
| 19 |
of the tree that is needed to build a stage three with your current |
| 20 |
package manager. You don't necessarily have to prune down the snapshot, |
| 21 |
but at least you want to ensure that the essential stage three disfiles |
| 22 |
remain mirrored so that the snapshots remain useful. |
| 23 |
-- |
| 24 |
Thanks, |
| 25 |
Zac |
Archives