--- xml/htdocs/proj/en/glep/glep-0060.html 2010/01/13 00:35:49 1.4 +++ xml/htdocs/proj/en/glep/glep-0060.html 2010/01/13 00:55:06 1.5 @@ -4,7 +4,7 @@ - + GLEP 60 -- Manifest2 filetypes @@ -27,9 +27,9 @@ Title:Manifest2 filetypes -Version:1.3 +Version:1.6 -Last-Modified:2008/10/28 07:46:51 +Last-Modified:2010/01/13 00:54:50 Author:Robin Hugh Johnson <robbat2 at gentoo.org> @@ -43,11 +43,11 @@ Created:November 2007 -Updated:June 2008, July 2008, October 2008 +Updated:June 2008, July 2008, October 2008, January 2010 Updates:44 -Post-History: +Post-History:December 2009 @@ -116,8 +116,8 @@

When generating or validating a Manifest, or commiting to a version control system, the package manager should endeavour to ignore files created by a version control system, backup files from text editors. A -non-exhaustive list is suggested here: CVS/, .svn/, .bzr/, -.git/, .hg/, .#*, *.rej, *.orig, *.bak, *~.

+non-exhaustive list is suggested here: CVS/, .svn/, .bzr/, +.git/, .hg/, .#*, *.rej, *.orig, *.bak, *~.

Additionally, for a transitional Manifest1->Manifest2 system, old-style digest files located in a 'files/' directory, may be excluded from Manifest2 generation, or included with a type of MISC.

@@ -192,7 +192,7 @@
@@ -235,7 +235,6 @@
@@ -255,6 +254,8 @@ filetype.
  • This filetype should be used for the scripts directories of a repository for important files.
  • +
  • This filetype is not limited to being used in the files/ +subdirectory.
  • @@ -263,6 +264,10 @@
  • uses _CRIT.
  • All other files that are not covered by another type should be considered as 'OTHER'.
  • +
  • Any further new filetypes should be introduced to subtract files +from the 'OTHER' set.
  • +
  • If a package manager runs into a unknown Manifest2 type, it should +be treated as 'OTHER'.
  • @@ -271,25 +276,26 @@

    If repeated use of a common path prefix is considered a bloat problem, a Manifest file should be added inside the common directory, however this should not be done blindly, as bloat by inodes is more significant for -the majority of use cases.

    +the majority of use cases. See also [#GLEP58] on size reductions of +Manifests.

    Chosing a filetype

    1. -
      matches Manifest
      +
      matches Manifest

      => MANIFEST, stop.

    2. -
      matches *.ebuild
      +
      matches *.ebuild

      => EBUILD, stop.

    3. -
      matches *.eclass
      +
      matches *.eclass

      => ECLASS, stop.

      @@ -301,25 +307,25 @@
    4. -
      matches files/*
      +
      matches files/*

      => AUX, continue [see note].

    5. -
      matches any of *.sh, *.bashrc, *.patch, ...
      +
      matches any of *.sh, *.bashrc, *.patch, ...

      => EXEC, stop.

    6. -
      matches any of metadata/cache/*, profiles/, package.*, use.mask*, ...
      +
      matches any of metadata/cache/*, profiles/, package.*, use.mask*, ...

      => DATA, stop.

    7. -
      matches any of ChangeLog, metadata.xml, *.desc, ...
      +
      matches any of ChangeLog, metadata.xml, *.desc, ...

      => MISC, stop.

      @@ -336,6 +342,8 @@ (Consider epatch given a directory of patches ${FILESDIR}/${PV}/, where it blindly includes them, or alternatively, the package.mask file or a profile being altered/missing).

      +

      The above lists of file patterns are not intended to be exhaustive, +but merely demonstrative.

      Note: The AUX entries should only be generated if we are generating a compatible Manifest that supports older versions of Portage. They should be generated along with the new type.

      @@ -379,7 +387,7 @@