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 @@
_CRIT is based off the _INFO type.
The modification or absence of a file listed as a _CRIT-derived type
-must be treated as an error.
+MUST be treated as an error.
@@ -235,7 +235,6 @@
This type shall be used for all eclasses only.
TODO: What about patches etc under eclasses/? Probably EXEC?
@@ -255,6 +254,8 @@
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/
@@ -263,6 +264,10 @@
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