1 |
Ciaran McCreesh wrote: |
2 |
> On Mon, 28 Sep 2009 20:23:34 +0200 |
3 |
> Sebastian Pipping <webmaster@××××××××.org> wrote: |
4 |
>> Now please ask questions and let us know what you think. |
5 |
> |
6 |
> Here's an alternative idea: |
7 |
> |
8 |
> * Move the repository information into the overlays themselves. Require |
9 |
> overlays to provide a file containing the description, homepage, |
10 |
> owner information etc. |
11 |
|
12 |
I have created another script yesterday that can auto-merge information |
13 |
from gitosis.conf into repositories.xml. With that script in a Git hook |
14 |
setting up new Git-based Gentoo-hosted overlays requires changes at only |
15 |
an single place and propagates to repositories.xml and |
16 |
layman-global.txt. (The only extension needed to make it work is adding |
17 |
a line "gentoo-is-overlay = True" to Git repos that are overlays in |
18 |
gitosis.conf. The "gentoo-" prefix is meant as a namespace and gitosis |
19 |
upstream confirmed that this works without interfering with gitosis itself.) |
20 |
|
21 |
At the moment moving overlay meta info into the overlays does not seem |
22 |
like a good idea to. It would mean that any script working with |
23 |
overlays needs to check the repo out to get to that data. That doesn't |
24 |
sound like fun to me. |
25 |
|
26 |
|
27 |
> Sounds like a perfect opportunity to make sure that everything in |
28 |
> layman's still actively maintained and developed. |
29 |
|
30 |
Let me second that. |
31 |
|
32 |
|
33 |
|
34 |
Sebastian |