| 1 |
On Wednesday 25 March 2009 22:34:00 Caleb Cushing wrote: |
| 2 |
> The basic idea is to be able to easily use overlays (without layman). |
| 3 |
> I believe this to be a pre-req to the "Cache Sync" idea listed on the |
| 4 |
> wiki. |
| 5 |
> |
| 6 |
> each repo should be able to have a differently defined way of sync-ing |
| 7 |
> (within predefined standards), I think they should also be capable of |
| 8 |
> defining the way that Manifests are handled (I don't think git needs |
| 9 |
> more than distfile manifests, other vcs may be similar). Supported |
| 10 |
> repository types should include rsync, git, svn, hg, bzr, darcs, cvs. |
| 11 |
|
| 12 |
Iirc portage can already sync from rsync, cvs and git |
| 13 |
|
| 14 |
> each SYNC_METHOD should be isolated from the others in code so that |
| 15 |
> they can be improved/extended easily. |
| 16 |
> |
| 17 |
> comments, additions welcome |
| 18 |
|
| 19 |
I think we can reuse the paludis concept of master_repository or we can |
| 20 |
implement a repository inheritance concept. |
| 21 |
So we can have a derived repository that get the parent repository eclasses |
| 22 |
and profiles as base. |
| 23 |
|
| 24 |
-- |
| 25 |
Timothy `Drizzt` Redaelli |
| 26 |
FreeSBIE Developer, Gentoo Developer, GUFI Staff |
| 27 |
There are two major products that come out of Berkeley: LSD and UNIX. |
| 28 |
We don't believe this to be a coincidence. -- Jeremy S. Anderson |
Archives