W dniu czw, 08.02.2018 o godzinie 17∶25 +0000, użytkownik M. J. Everitt napisał: > On 08/02/18 17:09, Michał Górny wrote: > > Remove the limitation that all files covered by the Manifest must reside > > on a single filesystem. This breaks valid uses of overlayfs without > > providing any real advantage. > > > > The removal is justified further in the updated rationale section. > > --- > > glep-0074.rst | 66 > > +++++++++++++++++++++++++++++++++++------------------------ > > 1 file changed, 39 insertions(+), 27 deletions(-) > > > > RST: https://dev.gentoo.org/~mgorny/tmp/glep-0074.rst > > HTML: https://dev.gentoo.org/~mgorny/tmp/glep-0074.html > > > > diff --git a/glep-0074.rst b/glep-0074.rst > > index 3835247..2f8deb2 100644 > > --- a/glep-0074.rst > > +++ b/glep-0074.rst > > @@ -6,10 +6,10 @@ Author: Michał Górny <mgo...@gentoo.org>, > > Ulrich Müller <u...@gentoo.org> > > Type: Standards Track > > Status: Final > > -Version: 1 > > +Version: 1.1 > > Created: 2017-10-21 > > -Last-Modified: 2017-12-16 > > -Post-History: 2017-10-26, 2017-11-16 > > +Last-Modified: 2018-02-08 > > +Post-History: 2017-10-26, 2017-11-16, 2018-02-08 > > Content-Type: text/x-rst > > Requires: 59, 61 > > Replaces: 44, 58, 60 > > @@ -126,13 +126,6 @@ a different file type. If the tree contain files of > > other types > > that are not otherwise ignored, they need to be covered by an explicit > > ``IGNORE``. > > > > -All the local (non-``DIST``) files covered by a Manifest tree must > > -reside on the same filesystem. It is an error to specify entries > > -applying to files on another filesystem. If files or directories that > > -are not otherwise ignored reside on a different filesystem, or symbolic > > -links point to targets on a different filesystem, they must > > -be explicitly excluded via ``IGNORE``. > > - > > > > Path and filename encoding > > -------------------------- > > @@ -325,22 +318,18 @@ Algorithm for finding parent Manifests > > In order to find the top-level Manifest from the current directory > > the following algorithm can be used: > > > > -1. Store the current directory as *original* and the device ID > > - of the containing filesystem (``st_dev``) as *startdev*, > > - > > -2. If the device ID of the containing filesystem (``st_dev``) > > - of the current directory is different than *startdev*, stop. > > +1. Store the current directory as *original*, > > > > -3. If the current directory contains a ``Manifest`` file: > > +2. If the current directory contains a ``Manifest`` file: > > > > a. If an ``IGNORE`` entry in the ``Manifest`` file covers > > the *original* directory (or one of the parent directories), stop. > > > > b. Otherwise, store the current directory as *last_found*. > > > > -4. If the current directory is the root system directory (``/``), stop. > > +3. If the current directory is the root system directory (``/``), stop. > > > > -5. Otherwise, enter the parent directory and jump to step 2. > > +4. Otherwise, enter the parent directory and jump to step 2. > > > > Once the algorithm stops, *last_found* will contain the relevant > > top-level Manifest. If *last_found* is null, then the directory tree > > > > <snip> > > Observation: does RST not support auto-numbering like other formats? It > would make renumbering lists like this much easier (and from programming > experience, less error-prone). If not, #FEATUREREQ ... :]
The whole purpose of WYWIWYG is to write *proper* text and not some magical syntax that magically gets transformed to auto-numbered list. Except when the format doesn't get it right. Also, this comment is entirely off-topic and not useful to the thread at all. Please cease those pointless off-topics. -- Best regards, Michał Górny
