Gentoo Archives: gentoo-dev

From: Nicolas Sebrecht <nsebrecht@×××××.fr>
To: gentoo-dev@l.g.o
Cc: Nicolas Sebrecht <nsebrecht@×××××.fr>
Subject: [gentoo-dev] Re: Portage Git migration - clean cut or git-cvsserver
Date: Fri, 01 Jun 2012 13:26:42
Message-Id: 20120601132545.GA2416@nicolas-desktop
In Reply to: [gentoo-dev] Re: Portage Git migration - clean cut or git-cvsserver by Duncan <>
The 01/06/12, Duncan wrote:

> But it seems to me that overlays are the primary use case for commits to > public trees other than gentoo first. Otherwise, the whole rebase-vs- > merge problem goes away, because the first public commit is to the gentoo > tree. But especially with overlays (like kde) that have an overlay- > first, test, then gentoo-tree, policy, that public overlay tree (which is > already in git) is part of the process. Commits MUST go thru the overlay > to get to the tree, and that overlay is public, so constant rebasing is a > definite no-no.
The purpose of overlays is to have ebuilds maintained outside of the official Gentoo portage. Importing a ebuild from an overlay whether it uses Git or not means importing the ebuild(s). In the Git context, it means the Gentoo maintainer has to make an import commit the same way it would be done to start a project with somthing like: cp 'files to be commited' . git add . git commit -m 'initial import' So, like explained before your concern is clearly out of the current discussion. Importing commit history from Overlays is not supported and will probably never be. Gentoo doesn't forces (and doesn't want to) overlays maintainers to use Git. -- Nicolas Sebrecht