From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] GLEP 74 post-Council review update [v3]
Date: Tue, 21 Nov 2017 19:20:37 +0100 [thread overview]
Message-ID: <23060.28277.709048.325922@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <1511285178.1074.13.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
>>>>> On Tue, 21 Nov 2017, Michał Górny wrote:
> All paths specified 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]_. It is an error to use Manifest files in directories
> containing files whose names contain the disallowed characters.
> The forward slash (``/``) must be used as path separator.
In addition to whitespace, you should also exclude C0 controls (U+0000
to U+001F), DEL (U+007F), and C1 controls (U+0080 to U+009F).
Rationale, these control characters can leave the user's terminal
in an unusable state when a package manager tries to output such a
filename in a message. As you reserve the backslash for a future
escape mechanism, this shouldn't be a too severe restriction.
Ulrich
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2017-11-21 18:20 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 [this message]
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
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=23060.28277.709048.325922@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