Gentoo Archives: gentoo-scm

From: Nirbheek Chauhan <nirbheek.chauhan@×××××.com>
To: "Michał Górny" <gentoo@××××××××××.pl>
Cc: gentoo-scm@l.g.o
Subject: Re: [gentoo-scm] Thin Manifests for git
Date: Mon, 19 Apr 2010 13:45:59
In Reply to: Re: [gentoo-scm] Thin Manifests for git by "Michał Górny"
On Mon, Apr 19, 2010 at 6:43 PM, Michał Górny <gentoo@××××××××××.pl> wrote:
> On Mon, 19 Apr 2010 08:21:27 +0200 > Fabian Groffen <grobian@g.o> wrote: > >> On 18-04-2010 23:52:34 +0200, Michał Górny wrote: >> > I've did as much as I could without getting more information, and >> > turning everything around. What it can is: >> > 1) Detect '.git' and enable Thin Manifests (only dirty check), >> >> how about we use a file like manifest1_obsolete to switch from fat to >> thin? > > Well, you are indeed right that the switch should be performed > on a better fine-tuned basis as with the current solution, developers > would have to manually trick portage into generating full Manifests for > their current GIT repositories. > > Have you got any suggestions regarding the filename? >
I think manifest1_obsolete in the root directory of the ebuild repo should work. Keep in mind though, that the root of the git repo, and the root of the ebuild repo may not be the same. For instance; git repo root:;a=tree ebuild repo root:;a=tree;f=overlay;hb=HEAD Also, repoman may be called from anywhere inside the repository; not necessarily inside ${REPO}/${CATEGORY}/${PN} -- ~Nirbheek Chauhan Gentoo GNOME+Mozilla Team