public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] GLEP 74 post-Council review update [v4]
Date: Wed, 22 Nov 2017 21:41:56 +0100	[thread overview]
Message-ID: <23061.57620.868522.993612@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <1511369657.8591.1.camel@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2026 bytes --]

>>>>> On Wed, 22 Nov 2017, Michał Górny wrote:

> Path and filename encoding
> --------------------------

> The path fields in the Manifest file must consist of characters
> corresponding to valid UTF-8 code points excluding the NULL character
> (``U+0000``), the backwards slash (``\``) and characters classified
> as whitespace in the current version of the Unicode standard
> [#UNICODE]_.

As I said before, all C0 and C1 control characters and DEL should be
excluded as well, i.e. 0x00 to 0x1f, 0x7f, and 0x80 to 0x9f. Allowing
such characters in what is basically a text file is only asking for
trouble.

> Any of the excluded characters that are present in path must be encoded
> using one of the following escape sequences:

> - characters in the ``U+0000`` to ``U+007F`` range can be encoded
>   as ``\xHH`` where ``HH`` specifies the zero-padded, hexadecimal
>   character code,

> - characters in the ``U+0000`` to ``U+FFFF`` range can be encoded
>   as ``\uHHHH`` where ``HHHH`` specifies the zero-padded, hexadecimal
>   character code,

> - characters in the UCS-4 range can be encoded as ``\UHHHHHHHH``
>   where ``HHHHHHHH`` specifies the zero-padded, hexadecimal character
>   code.

> It is invalid for backwards slash to be used in any other context,
> and a backwards slash present in filename must be encoded. Backwards
> slash used as path component separator should be replaced by forward
> slash instead.

This entire section about the escape mechanism should be clearly
labelled as being purely optional, as it is not relevant for Gentoo
(and would break backwards compatibility with existing package
manager implementations). Maybe add a reference to GLEP 31 too?

> The encoding can be used for other characters as well. In particular,
> escaping control characters is recommended to ensure that the file
> works correctly in text editors.

See above, this should not be "recommended", but literal control chars
should be strictly forbidden.

Ulrich

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2017-11-22 20:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 10:19 [gentoo-dev] [RFC] GLEP 74 post-Council review update Michał Górny
2017-11-17 20:37 ` Daniel Campbell
2017-11-20 17:24   ` Michał Górny
2017-11-20 18:42 ` [gentoo-dev] [RFC] GLEP 74 post-Council review update [v2] Michał Górny
2017-11-20 21:37   ` Ulrich Mueller
2017-11-21  6:30     ` Ulrich Mueller
2017-11-21 17:14     ` Michał Górny
2017-11-21 20:28       ` Ulrich Mueller
2017-11-21 21:13         ` Michał Górny
2017-11-21 21:48           ` Ulrich Mueller
2017-11-21 23:51             ` Michał Górny
2017-11-22  5:43               ` Ulrich Mueller
2017-11-22  2:59   ` R0b0t1
2017-11-22  8:02     ` Michał Górny
2017-11-22 16:38       ` R0b0t1
2017-11-21 17:26 ` [gentoo-dev] [RFC] GLEP 74 post-Council review update [v3] Michał Górny
2017-11-21 18:20   ` Ulrich Mueller
2017-11-21 18:22     ` Michał Górny
2017-11-22 16:54 ` [gentoo-dev] [RFC] GLEP 74 post-Council review update [v4] Michał Górny
2017-11-22 20:41   ` Ulrich Mueller [this message]
2017-11-23 20:53 ` [gentoo-dev] [RFC] GLEP 74 post-Council review update [v5] Michał Górny
2017-12-01 11:30   ` Fabian Groffen
2017-12-01 12:32     ` Michał Górny

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=23061.57620.868522.993612@a1i15.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox