1 |
On Fri, Jun 1, 2012 at 9:25 AM, Nicolas Sebrecht <nsebrecht@×××××.fr> wrote: |
2 |
> So, like explained before your concern is clearly out of the current |
3 |
> discussion. Importing commit history from Overlays is not supported and |
4 |
> will probably never be. Gentoo doesn't forces (and doesn't want to) |
5 |
> overlays maintainers to use Git. |
6 |
|
7 |
I'm not sure that git even supports this, unless the overlay is a |
8 |
complete clone of the entire gentoo-x86.git repository. |
9 |
|
10 |
I think the way git operations work is by finding common parents in |
11 |
the history of two heads, and then moving forward from there. If you |
12 |
have two completely different repositories then they never will have a |
13 |
common parent. |
14 |
|
15 |
Plus, even if it did work, to rebase the overlay on the gentoo-x86 |
16 |
repository you'd have to import the full gentoo-x86 tree into it. |
17 |
Then you'd have to push EVERYTHING in your overlay into gentoo-x86. I |
18 |
don't think you can just push individual files from one tree to |
19 |
another. |
20 |
|
21 |
From what I've seen the various methods out there which do involve |
22 |
moving only part of one branch into another basically involve a LOT of |
23 |
history manipulation or are really no different than just copying the |
24 |
files into the branch and adding them, losing all history in the |
25 |
process. |
26 |
|
27 |
I'm not sure how important all that history preservation actually is - |
28 |
the overlay would still possess it. If we did want to preserve it |
29 |
then the only practical option I see is to have the overlay start out |
30 |
as a clone of gentoo-x86 and keep around all the non-overlay packages, |
31 |
which then means that anybody using the overlay will get all those old |
32 |
gentoo-x86 packages as part of their portage tree. Plus you still |
33 |
have the rebase+gpg-signatures=fail issue. |
34 |
|
35 |
Rich |