1 |
On 20:55 Sat 06 Aug , Robin H. Johnson wrote: |
2 |
> Everything you have mentioned here was previously covered in the |
3 |
> discussions about Git conversion models. Please consult the history of |
4 |
> this list, as well as the -scm list. Additionally, a large discussion |
5 |
> about the pros and cons of all 3 models (package per repo, category |
6 |
> per repo, single repo) was had at the GSoC mentor summit last year, |
7 |
> and a number of the core Git developers were involved in the |
8 |
> discussion. |
9 |
|
10 |
While noting the above [1 and its thread], I'd also like to point out |
11 |
that git submodules are conceptually a good fit but the implementation |
12 |
is lacking. Two examples: |
13 |
|
14 |
- Creating new submodules requires administrative rights on the server. |
15 |
You can't just add one and push it up. This could conceivably be fixed |
16 |
by a hook that ran a specific privileged command to add a submodule, but |
17 |
I'm not really sure how or whether it's currently possible given the |
18 |
times available to run hooks. |
19 |
|
20 |
- What we'd really want with submodules is to have the primary object |
21 |
storage shared in the master repo rather than in the submodule. That way |
22 |
we'd benefit from compression across packages, and furthmore, package |
23 |
moves wouldn't duplicate history. |
24 |
|
25 |
If you're interested in fixing the above problems as well as the ones |
26 |
that exist regardless of repo format (linked on the main tracker bug |
27 |
[2]), then submodules could become a better option. |
28 |
|
29 |
-- |
30 |
Thanks, |
31 |
Donnie |
32 |
|
33 |
Donnie Berkholz |
34 |
Council Member / Sr. Developer |
35 |
Gentoo Linux |
36 |
Blog: http://dberkholz.com |
37 |
|
38 |
1. http://archives.gentoo.org/gentoo-scm/msg_98932c55ec10fcc5445ab950e62b12dc.xml |
39 |
2. https://bugs.gentoo.org/show_bug.cgi?id=333531 |