Gentoo Archives: gentoo-portage-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-portage-dev@l.g.o
Subject: Re: [gentoo-portage-dev] Re: [gentoo-commits] proj/portage:master commit in: bin/
Date: Tue, 13 Sep 2011 05:50:48
Message-Id: 4E6EEF26.3090408@gentoo.org
In Reply to: Re: [gentoo-portage-dev] Re: [gentoo-commits] proj/portage:master commit in: bin/ by Zac Medico
1 On 09/12/2011 10:30 PM, Zac Medico wrote:
2 > On 09/12/2011 09:38 PM, Robin H. Johnson wrote:
3 >> On Tue, Sep 13, 2011 at 03:20:35AM +0000, Zac Medico wrote:
4 >>> commit: 677240f7b3db66bdcd403c214e5d3fa30e31a24a
5 >>> Author: Zac Medico <zmedico <AT> gentoo <DOT> org>
6 >>> AuthorDate: Tue Sep 13 03:20:00 2011 +0000
7 >>> Commit: Zac Medico <zmedico <AT> gentoo <DOT> org>
8 >>> CommitDate: Tue Sep 13 03:20:00 2011 +0000
9 >>> URL: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=677240f7
10 >>>
11 >>> repoman: don't sign thin manifests
12 >>>
13 >>> Thin manifests imply reliance on the VCS for file integrity,
14 >>> which implies that manifest signatures are not needed.
15 >>
16 >> This is only true after the VCS has signed commits.
17 >>
18 >> If the VCS does not have signed commits, then we should have this
19 >> signature.
20 >
21 > So, should we add the ability to set "signed-manifests = false" in
22 > metadata/layout.conf? I can imagine that people using thin-manifests
23 > typically don't want signed-manifests, since it tends the introduce
24 > merge conflicts like those that thin-manifests is supposed to avoid.
25
26 I've implemented "signed-manifests = false" here:
27
28 http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=9cb089047e10b300100e7bbdc4274ecf8866b0bb
29
30 --
31 Thanks,
32 Zac

Replies