On Sun, 10 Apr 2016 18:21:44 -0400 Michael Orlitzky <m...@gentoo.org> wrote:
> On 04/10/2016 05:36 PM, Gordon Pettey wrote: > > Or you could just use a branching workflow like Git has great > > support for, and create your overlay as a branch of the main tree > > you're copying ebuilds from. With recent versions, you can even > > have checkouts of different branches from the same tree in > > different directories, so you're not duplicating the the whole > > repository. Then you could just git diff from the master branch, > > and no need for preserving CVS misbehavior. > > I suggested this on the bug, but it's not so clear-cut. With a branch, > you have a million other ebuilds sitting around in "your overlay" that > you don't care about. I'm also not sure how the metadata updates would > work; like, if it would be efficient to pull the rsync metadata and > then run `emerge --metadata` or something like that. It wouldn't be > fair to say "just use a branch!" if that's going to mean that > somebody's day-to-day work gets a lot slower. Would a sparse checkout help here? I've used this feature in a different context. You could add the packages you do care about to the sparse checkout list. http://stackoverflow.com/questions/600079/is-there-any-way-to-clone-a-git-repositorys-sub-directory-only/13738951#13738951 -- James Le Cuirot (chewi) Gentoo Linux Developer
pgprLYJIC7D0v.pgp
Description: OpenPGP digital signature
