/[gentoo]/xml/htdocs/proj/en/glep/glep-0058.txt
Gentoo

Diff of /xml/htdocs/proj/en/glep/glep-0058.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.4 Revision 1.5
1GLEP: 58 1GLEP: 58
2Title: Security of distribution of Gentoo software - Infrastructure to User distribution - MetaManifest 2Title: Security of distribution of Gentoo software - Infrastructure to User distribution - MetaManifest
3Version: $Revision: 1.4 $ 3Version: $Revision: 1.5 $
4Last-Modified: $Date: 2008/10/28 07:45:27 $ 4Last-Modified: $Date: 2010/01/13 00:57:49 $
5Author: Robin Hugh Johnson <robbat2@gentoo.org>, 5Author: Robin Hugh Johnson <robbat2@gentoo.org>,
6Status: Draft 6Status: Draft
7Type: Standards Track 7Type: Standards Track
8Content-Type: text/x-rst 8Content-Type: text/x-rst
9Requires: 44, 60 9Requires: 44, 60
10Created: October 2006 10Created: October 2006
11Updated: November 2007, June 2008, July 2008, October 2008 11Updated: November 2007, June 2008, July 2008, October 2008, January 2010
12Post-History: 12Post-History: Decemeber 2009
13 13
14======== 14========
15Abstract 15Abstract
16======== 16========
17MetaManifest provides a means of verifiable distribution from Gentoo 17MetaManifest provides a means of verifiable distribution from Gentoo
124The above does not conflict the proposal contained in GLEP33, which 124The above does not conflict the proposal contained in GLEP33, which
125restructure eclasses to include subdirectories and Manifest files, as 125restructure eclasses to include subdirectories and Manifest files, as
126the Manifest rules above still provide indirect verification for all 126the Manifest rules above still provide indirect verification for all
127files after the GLEP33 restructuring if it comes to pass. 127files after the GLEP33 restructuring if it comes to pass.
128 128
129If other Manifests are added (such as per-category, or protecting 129If other Manifests are added (such as per-category, per first-level
130versioned eclases), the size of the MetaManifest will be greatly 130directory, or protecting versioned eclases), the size of the
131reduced, and this specification was written with such a possible future 131MetaManifest will be greatly reduced, and this specification was written
132addition in mind. 132with such a possible future addition in mind.
133 133
134MetaManifest generation will take place as part of the existing process 134MetaManifest generation will take place as part of the existing process
135by infrastructure that takes the contents of CVS and prepares it for 135by infrastructure that takes the contents of CVS and prepares it for
136distribution via rsync, which includes generating metadata. In-tree 136distribution via rsync, which includes generating metadata. In-tree
137Manifest files are not checked at this point, as they are assumed to be 137Manifest files are not checked at this point, as they are assumed to be
244-------------------------------- 244--------------------------------
245MetaManifest size considerations 245MetaManifest size considerations
246-------------------------------- 246--------------------------------
247With only two levels of Manifests (per-package and top-level), every 247With only two levels of Manifests (per-package and top-level), every
248rsync will cause a lot of traffic transfering the modified top-level 248rsync will cause a lot of traffic transfering the modified top-level
249MetaManifest. To reduce this, per-category Manifests are strongly 249MetaManifest. To reduce this, first-level directory Manifests are
250recommended. Alternatively, if the distribution method efficently 250strongly recommended. Alternatively, if the distribution method
251handles small patch-like changes in an existing file, using an 251efficently handles small patch-like changes in an existing file,
252uncompressed MetaManifest may be acceptable (this would primarily be 252using an uncompressed MetaManifest may be acceptable (this would
253distributed version control systems). Other suggestions in reducing this 253primarily be distributed version control systems). Other suggestions
254traffic are welcomed. 254in reducing this traffic are welcomed.
255 255
256======================= 256=======================
257Backwards Compatibility 257Backwards Compatibility
258======================= 258=======================
259- There are no backwards compatibility issues, as old versions of 259- There are no backwards compatibility issues, as old versions of

Legend:
Removed from v.1.4  
changed lines
  Added in v.1.5

  ViewVC Help
Powered by ViewVC 1.1.20