On 04/07/2010 05:58 AM, Angelo Arrifano wrote:
3*) With git, one would just branch (lets call it embedded branch) the
package. Apply the patches there and let people using embedded profiles
to emerge from that branch instead of master.
Benefits? I think they are pretty obvious - people can start putting
quick patches in the tree for specific arches while not breaking others.
IMHO, the only bottleneck I see on Gentoo development is the massive
policy (not saying it is not needed) a -dev has to follow just to commit
a simple fix. Git my friends, will be our holly grail.
I think that allowing for different levels of QA standards, and
accomodating things like this are good reasons to use branches.
HOWEVER, we do need to manage this so that it doesn't get out of hand.
We really don't want users following 14 different branches and have 10
different variations on every package in the tree - which is how it
could get after a year or two of branching without any effort to do
pruning and get things merged into a main tree.
Having branches to do development and facilitate access and testing
seems fine, however we should always have the goal of getting these
tested revisions merged back into the main tree. We really don't want
divergent development to be the norm.
