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

Replies