public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Arthur Zamarin <arthurzam@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org,  glep@gentoo.org
Subject: [gentoo-dev] Re: [DRAFT] GLEP 84: Standard format for package.mask files
Date: Thu, 05 Oct 2023 20:40:52 +0200	[thread overview]
Message-ID: <ufs2oyksr@gentoo.org> (raw)
In-Reply-To: <f7a7ecd5-9c12-4af5-a202-b133e137d3e9@gentoo.org> (Arthur Zamarin's message of "Wed, 4 Oct 2023 21:43:26 +0300")

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

>>>>> On Wed, 04 Oct 2023, Arthur Zamarin wrote:

> Files can decide to add some extra file documentation, in which case, the
> entries start after the line:

>     #--- END OF EXAMPLES ---

This agrees with current package.mask, but seems rather specific.
Instead of reinventing the wheel, maybe a "scissors line" could be used,
i.e. a line consisting mainly of "-", ">8" and "8<", similar to the line
used by git-mailinfo?

I'm also wondering if we shouldn't have a similar marker for the end of
the mask entries, i.e. everything after it would be ignored. This isn't
currently needed for package.mask, but other files in profiles have an
Emacs local variables block or a Vim modeline at the end.

Ulrich

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]

  parent reply	other threads:[~2023-10-05 18:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 18:43 [gentoo-dev] [DRAFT] GLEP 84: Standard format for package.mask files Arthur Zamarin
2023-10-05  3:12 ` Michał Górny
2023-10-05 18:49   ` Arthur Zamarin
2023-10-05 19:36     ` Ulrich Mueller
2023-10-05 19:31   ` Arthur Zamarin
2023-10-05 19:44   ` Ulrich Mueller
2023-10-05 18:40 ` Ulrich Mueller [this message]
2023-10-05 19:19   ` [gentoo-dev] " Arthur Zamarin

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=ufs2oyksr@gentoo.org \
    --to=ulm@gentoo.org \
    --cc=arthurzam@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=glep@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