Gentoo Archives: gentoo-commits

From: "Robin H. Johnson (robbat2)" <robbat2@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] gentoo commit in users/robbat2/tree-signing-gleps: 01-distribution-process-security
Date: Thu, 09 Oct 2008 22:30:47
Message-Id: E1Ko41s-0000Nc-Tn@stork.gentoo.org
1 robbat2 08/10/09 22:30:44
2
3 Modified: 01-distribution-process-security
4 Log:
5 Add note per-category MetaManifests reducing delta requirements.
6
7 Revision Changes Path
8 1.23 users/robbat2/tree-signing-gleps/01-distribution-process-security
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/users/robbat2/tree-signing-gleps/01-distribution-process-security?rev=1.23&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/users/robbat2/tree-signing-gleps/01-distribution-process-security?rev=1.23&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/users/robbat2/tree-signing-gleps/01-distribution-process-security?r1=1.22&r2=1.23
13
14 Index: 01-distribution-process-security
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/users/robbat2/tree-signing-gleps/01-distribution-process-security,v
17 retrieving revision 1.22
18 retrieving revision 1.23
19 diff -p -w -b -B -u -u -r1.22 -r1.23
20 --- 01-distribution-process-security 9 Oct 2008 21:33:11 -0000 1.22
21 +++ 01-distribution-process-security 9 Oct 2008 22:30:44 -0000 1.23
22 @@ -1,7 +1,7 @@
23 GLEP: xx+1
24 Title: Security of distribution of Gentoo software - Infrastructure to User distribution - MetaManifest
25 -Version: $Revision: 1.22 $
26 -Last-Modified: $Date: 2008/10/09 21:33:11 $
27 +Version: $Revision: 1.23 $
28 +Last-Modified: $Date: 2008/10/09 22:30:44 $
29 Author: Robin Hugh Johnson <robbat2@g.o>,
30 Status: Draft
31 Type: Standards Track
32 @@ -236,6 +236,18 @@ decide is the tree is too out of date pe
33 verification process. The decision about freshness should be a
34 user-configuration setting, with the ability to override.
35
36 +--------------------------------
37 +MetaManifest size considerations
38 +--------------------------------
39 +With only two levels of Manifests (per-package and top-level), every
40 +rsync will cause a lot of traffic transfering the modified top-level
41 +MetaManifest. To reduce this, per-category Manifests are strongly
42 +recommended. Alternatively, if the distribution method efficently
43 +handles small patch-like changes in an existing file, using an
44 +uncompressed MetaManifest may be acceptable (this would primarily be
45 +distributed version control systems). Other suggestions in reducing this
46 +traffic are welcomed.
47 +
48 =======================
49 Backwards Compatibility
50 =======================