public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Arthur Zamarin <arthurzam@gentoo.org>
To: gentoo-dev@lists.gentoo.org, "Michał Górny" <mgorny@gentoo.org>,
	glep@gentoo.org
Subject: Re: [gentoo-dev] [DRAFT] GLEP 84: Standard format for package.mask files
Date: Thu, 5 Oct 2023 22:31:21 +0300	[thread overview]
Message-ID: <146343b5-9513-441a-ab4c-5af858735df5@gentoo.org> (raw)
In-Reply-To: <d274c068048a58a24b948e0c10ecfa43b54eab6d.camel@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 934 bytes --]

On 05/10/2023 06.12, Michał Górny wrote:
> On Wed, 2023-10-04 at 21:43 +0300, Arthur Zamarin wrote:
>> Specification
>> =============
>>
>> ...
>>
>> Must conform to PMS sections 4.4 [#PMS-4.4]_ and 5.2.8 [#PMS-5.2.8]_. This GLEP
>> further limits the syntax to one item per line, without any leading or
>> proceeding whitespaces, no comments inside the packages list, and no blank
>> lines between items in the list.
> 
> That kinda sucks.  For very long masks, it is useful to be able to split
> the entry into subgroups.  I suppose it's technically still doable via
> splitting the entry but that sounds a bit backwards.
> 

Good point. I'll update the draft to allow single blank lines between
package lists, but I'll still add recommendation to consider splitting
into multiple separate masks.

-- 
Arthur Zamarin
arthurzam@gentoo.org
Gentoo Linux developer (Python, pkgcore stack, Arch Teams, GURU)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2023-10-05 19:32 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 [this message]
2023-10-05 19:44   ` Ulrich Mueller
2023-10-05 18:40 ` [gentoo-dev] " Ulrich Mueller
2023-10-05 19:19   ` 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=146343b5-9513-441a-ab4c-5af858735df5@gentoo.org \
    --to=arthurzam@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=glep@gentoo.org \
    --cc=mgorny@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