| 1 |
On 27 March 2015 at 10:32, Andreas K. Huettel <dilfridge@g.o> wrote: |
| 2 |
|
| 3 |
> It would be great to logically separate ebuild repositories (main tree and |
| 4 |
> overlays) somehow logically from code, data, ... |
| 5 |
> |
| 6 |
> How about adding an additional level "repo" for everything that contains |
| 7 |
> ebuild trees? |
| 8 |
> |
| 9 |
> repo/gentoo <<-- our main tree |
| 10 |
> repo/proj/kde |
| 11 |
> repo/proj/perl-overlay |
| 12 |
> repo/dev/dilfridge |
| 13 |
> |
| 14 |
> Everything else stays where it is, eg., |
| 15 |
> |
| 16 |
> data/glsa |
| 17 |
> proj/sandbox |
| 18 |
> proj/portage |
| 19 |
> ... |
| 20 |
> |
| 21 |
|
| 22 |
|
| 23 |
Agreed. It used to imply overlays by being called 'git.overlays.gentoo.org'. |
| 24 |
|
| 25 |
But but now its just going to be 'git.gentoo.org' .... |
| 26 |
|
| 27 |
And there's proj/ which is frankly dogs breakfast. |
| 28 |
|
| 29 |
Re-organising that to be sensible is a bit much to ask at this time. |
| 30 |
|
| 31 |
But maybe gentoo can at least start the ball rolling. |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
Kent |
| 36 |
|
| 37 |
*KENTNL* - https://metacpan.org/author/KENTNL |
Archives