--- xml/htdocs/proj/en/glep/glep-0044.html 2005/12/06 16:19:37 1.2 +++ xml/htdocs/proj/en/glep/glep-0044.html 2006/01/23 10:24:24 1.3 @@ -32,9 +32,9 @@ Title:Manifest2 format -Version:1.1 +Version:1.2 -Last-Modified:2005/12/06 03:34:21 +Last-Modified:2005/12/06 16:19:37 Author:Marius Mauch <genone at gentoo.org>, @@ -46,7 +46,7 @@ Created:04-Dec-2005 -Post-History:06-Dec-2005 +Post-History:06-Dec-2005, 23-Jan-2006 @@ -92,7 +92,7 @@ The main long term goals of this proposal are to:

Future portage improvements might extend this list (for example with types @@ -146,11 +146,11 @@ SHA1 1210160f7baf0319de3b1b58dc80d7680d316d28 MD5 732cdc3b41403a115970d497a9ec257e MISCFILE metadata.xml 269 RMD160 39d775de55f9963f8946feaf088aa0324770bacb SHA1 4fd7b285049d0e587f89e86becf06c0fd77bae6d MD5 82e806ed62f0596fb7bef493d225712f -SRCURI sylpheed-claws-1.0.5.tar.bz2 3268626 RMD160 f2708b5d69bc9a5025812511fde04eca7782e367 +DISTFILE sylpheed-claws-1.0.5.tar.bz2 3268626 RMD160 f2708b5d69bc9a5025812511fde04eca7782e367 SHA1 d351d7043eef7a875df18a8c4b9464be49e2164b MD5 ef4a1a7beb407dc7c31b4799bc48f12e -SRCURI sylpheed-claws-1.9.100.tar.bz2 3480063 RMD160 72fbcbcc05d966f34897efcc1c96377420dc5544 +DISTFILE sylpheed-claws-1.9.100.tar.bz2 3480063 RMD160 72fbcbcc05d966f34897efcc1c96377420dc5544 SHA1 47465662b5470af5711493ce4eaad764c5bf02ca MD5 863c314557f90f17c2f6d6a0ab57e6c2 -SRCURI sylpheed-claws-1.9.15.tar.bz2 3481018 RMD160 b01d1af2df55806a8a8275102b10e389e0d98e94 +DISTFILE sylpheed-claws-1.9.15.tar.bz2 3481018 RMD160 b01d1af2df55806a8a8275102b10e389e0d98e94 SHA1 a17fc64b8dcc5b56432e5beb5c826913cb3ad79e MD5 0d187526e0eca23b87ffa4981f7e1765

@@ -184,7 +184,7 @@

Removal of digest files

Normal users that don't use a "tuned" filesystem for the portage tree are -wasting several dozen to a few hundred megabytes of discspace with the current +wasting several dozen to a few hundred megabytes of disk space with the current system, largely caused by the digest files. This is due to the filesystem overhead present in most filesystem that have a standard blocksize of four kilobytes while most digest files are under @@ -192,7 +192,7 @@ per digest file (likely even more). At the time of this writing the tree contains roughly 22.000 digest files, so the overall waste caused by digest files is estimated at about 70-100 megabytes. -Furthermore it is assumed that this will also reduce the discspace wasted by +Furthermore it is assumed that this will also reduce the disk space wasted by the Manifest files as they now contain more content, but this hasn't been verified yet.

By unifying the digest files with the Manifest these tiny files are eliminated @@ -210,7 +210,7 @@

Removal of checksum collisions

-

The current system theoretically allows for a SRCURI type file to be recorded +

The current system theoretically allows for a DISTFILE type file to be recorded in multiple digest files with different sizes and/or checksums. In such a case one version of a package would report a checksum violation while another one would not. This could create confusion and uncertainity among users. @@ -221,7 +221,7 @@

Flexible verification system

Right now portage verifies the checksum of every file listed in the Manifest -before using any file of the package and all SRCURI files of an ebuild +before using any file of the package and all DISTFILE files of an ebuild before using that ebuild. This is unnecessary in many cases:

  • During the "depend" phase (when the ebuild metadata is generated) only @@ -234,7 +234,7 @@
  • Generally files of type MISCFILE don't need to be verified as they are only used in very specific situations, aren't executed (just parsed at most) and don't affect the package build process.
  • -
  • Files of type SRCURI only need to be verified directly after fetching and +
  • Files of type DISTFILE only need to be verified directly after fetching and before unpacking them (which often will be one step), not every time their associated ebuild is used.
@@ -320,7 +320,7 @@ like any other checksum. But so far no real benefit (other than a slightly more modular implementation) for this has been seen while it has several drawbacks: For once, unlike checksums, the size field is definitely required -for all SRCURI files, also it would slightly increase the length of +for all DISTFILE files, also it would slightly increase the length of each entry by adding a SIZE keyword.
  • removal of the MISCFILE type: It has been suggested to completely drop entries of type MISCFILE. This would result in a minor space reduction @@ -378,7 +378,7 @@