| 1 |
Rich Freeman wrote: |
| 2 |
> > Calling it "gentoo" makes sense |
| 3 |
> |
| 4 |
> The thing is, Gentoo is more than a bunch of ebuilds. |
| 5 |
|
| 6 |
Sure, but the gentoo ebuild repo is just a bunch of ebuilds. |
| 7 |
|
| 8 |
Gentoo as name can and should be used elsewhere too of course. |
| 9 |
|
| 10 |
> Certainly they're a HUGE part of Gentoo, but they alone aren't Gentoo. |
| 11 |
|
| 12 |
> In some sense you could have ebuilds/gentoo.git but then what happens |
| 13 |
> when you clone ebuilds/gentoo.git, website/gentoo.git, and so on? |
| 14 |
|
| 15 |
Keep them in different subdirectories, to reflect the central |
| 16 |
namespace? |
| 17 |
|
| 18 |
|
| 19 |
> Namespaces are useful to prevent accidental collisions, and for |
| 20 |
> organization, but without getting too crazy with the names I think it |
| 21 |
> is best off when the final name stands on its own reasonably well. |
| 22 |
|
| 23 |
Always optimize for the common case. What changes more often, |
| 24 |
ebuilds/ or website/ ? That repo gets to use the pretty name, |
| 25 |
the other repo gets an uglier one, maybe "website/website.git". :) |
| 26 |
|
| 27 |
|
| 28 |
//Peter |
Archives