1 |
On Fri, Jun 1, 2012 at 12:33 PM, Robin H. Johnson <robbat2@g.o> wrote: |
2 |
> What about overlay repositories that elect to be a branch of the main |
3 |
> tree via git? |
4 |
> |
5 |
> Do we call that forbidden usage? |
6 |
|
7 |
I think that branches off of the main tree are mainly going to be |
8 |
useful for more eclass/profile/etc-related work. Work on a package or |
9 |
small group of packages will almost always go better in a completely |
10 |
independent overlay. If you try to do that kind of work in a branch |
11 |
then if you create an rsync tree from that branch it will contain all |
12 |
the other packages that you aren't working on, and they'll get stale |
13 |
very quickly. Anybody using that as an overlay will get a bunch of |
14 |
old ebuilds for who-knows-what in their tree. |
15 |
|
16 |
Now, branches in the main tree are going to be really useful for stuff |
17 |
like package moves, new virtuals, eclass api changes, or other messy |
18 |
changes that have big tree-wide impacts. You can stage the change and |
19 |
fix the 300 impacted ebuilds in a branch, get lots of people to test |
20 |
them, and then merge those in with a single transaction, pulling in |
21 |
updates from master all the while. That is more about portage tree |
22 |
maintenance than package maintenance per-se. |
23 |
|
24 |
All that said, having the tree in git is still a big help to proxy |
25 |
maintainers and others even with all these issues. I've worked as an |
26 |
outside contributor to other projects and it is a lot easier with git. |
27 |
I can easily work in my own PM, rebase against their master, and then |
28 |
easily submit a nice clean diff as a patch, even without doing any |
29 |
pushing at all. I don't have to have push rights to anything official |
30 |
to be more efficient in my contributions. |
31 |
|
32 |
Rich |