--- xml/htdocs/proj/en/glep/glep-0058.html 2008/10/28 07:47:52 1.1 +++ xml/htdocs/proj/en/glep/glep-0058.html 2010/01/13 01:02:36 1.2 @@ -4,7 +4,7 @@ - + GLEP 58 -- Security of distribution of Gentoo software - Infrastructure to User distribution - MetaManifest @@ -27,9 +27,9 @@ Title:Security of distribution of Gentoo software - Infrastructure to User distribution - MetaManifest -Version:1.4 +Version:1.5 -Last-Modified:2008/10/28 07:45:27 +Last-Modified:2010/01/13 00:57:49 Author:Robin Hugh Johnson <robbat2 at gentoo.org>, @@ -43,9 +43,9 @@ Created:October 2006 -Updated:November 2007, June 2008, July 2008, October 2008 +Updated:November 2007, June 2008, July 2008, October 2008, January 2010 -Post-History: +Post-History:Decemeber 2009 @@ -175,10 +175,10 @@ restructure eclasses to include subdirectories and Manifest files, as the Manifest rules above still provide indirect verification for all files after the GLEP33 restructuring if it comes to pass.

-

If other Manifests are added (such as per-category, or protecting -versioned eclases), the size of the MetaManifest will be greatly -reduced, and this specification was written with such a possible future -addition in mind.

+

If other Manifests are added (such as per-category, per first-level +directory, or protecting versioned eclases), the size of the +MetaManifest will be greatly reduced, and this specification was written +with such a possible future addition in mind.

MetaManifest generation will take place as part of the existing process by infrastructure that takes the contents of CVS and prepares it for distribution via rsync, which includes generating metadata. In-tree @@ -287,12 +287,12 @@

MetaManifest size considerations

With only two levels of Manifests (per-package and top-level), every rsync will cause a lot of traffic transfering the modified top-level -MetaManifest. To reduce this, per-category Manifests are strongly -recommended. Alternatively, if the distribution method efficently -handles small patch-like changes in an existing file, using an -uncompressed MetaManifest may be acceptable (this would primarily be -distributed version control systems). Other suggestions in reducing this -traffic are welcomed.

+MetaManifest. To reduce this, first-level directory Manifests are +strongly recommended. Alternatively, if the distribution method +efficently handles small patch-like changes in an existing file, +using an uncompressed MetaManifest may be acceptable (this would +primarily be distributed version control systems). Other suggestions +in reducing this traffic are welcomed.

@@ -340,7 +340,7 @@