Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-scm
Navigation:
Lists: gentoo-scm: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-scm@g.o
From: Maciej Mrozowski <reavertm@...>
Subject: Re: Thin Manifests for git
Date: Mon, 19 Apr 2010 11:38:30 +0200
On Monday 19 of April 2010 08:21:27 Fabian Groffen 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?

Any reason for this?

It shouldn't cause any merge conflicts as the difference between 'fat' and 
'slim' are lines added/removed (I suppose DIST hashes would be generated in 
the same form as they are now, so SHA1, SHA256 and RMD160). It's just over-
complicating things imho.

Portage already is aware of scm vs rsync repositories as for instance some 
repoman checks are omitted for those scm ones. Therefore it seems correct to 
rely on this mechanism and let portage/repoman generate right (TM) Manifest 
for repository being used.

-- 
regards
MM


Replies:
Re: Thin Manifests for git
-- Fabian Groffen
References:
Re: Thin Manifests for git
-- Michał Górny
Re: Thin Manifests for git
-- Fabian Groffen
Navigation:
Lists: gentoo-scm: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Thin Manifests for git
Next by thread:
Re: Thin Manifests for git
Previous by date:
Re: Thin Manifests for git
Next by date:
Re: Thin Manifests for git


Updated May 23, 2012

Summary: Archive of the gentoo-scm mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.