From: Oskari Pirhonen <xxc3ncoredxx@gmail.com>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: Arthur Zamarin <arthurzam@gentoo.org>, gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Standard parsable format for profiles/package.mask file
Date: Thu, 21 Sep 2023 22:54:57 -0500 [thread overview]
Message-ID: <ZQ0QEbojCfyZD1-w@dj3ntoo> (raw)
In-Reply-To: <ujzsji5m4@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
On Thu, Sep 21, 2023 at 23:22:27 +0200, Ulrich Mueller wrote:
> >>>>> On Thu, 21 Sep 2023, Arthur Zamarin wrote:
>
> > ===== "Formal" format =====
>
> > Each entry is composed of 2 parts: "#"-prefixed explanation block and
> > list of "${CATEGORY}/${PN}" packages. Entries are separated when a new
> > explanation block starts (meaning first "#"-prefixed line after packages
> > list). You may add newlines between packages in packages list.
>
> "Must" rather than "may" here? You certainly cannot list several
> packages in the same line.
>
I read it to mean something like this would be allowed:
# Blurb about package1, package2, and package3
category/package1
category/package2
category/package3
Whether it makes sense to allow that is a different question.
- Oskari
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-09-22 3:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 19:40 [gentoo-dev] Standard parsable format for profiles/package.mask file Arthur Zamarin
2023-09-21 21:09 ` [gentoo-dev] " Florian Schmaus
2023-09-21 21:36 ` Ulrich Mueller
2023-09-21 21:48 ` Sam James
2023-09-22 6:39 ` Florian Schmaus
2023-09-22 6:53 ` Florian Schmaus
2023-09-22 9:46 ` Ulrich Mueller
2023-09-22 11:51 ` Ulrich Mueller
2023-09-22 14:01 ` Sam James
2023-09-22 14:26 ` Alex Boag-Munroe
2023-09-22 14:36 ` Sam James
2023-09-22 14:50 ` Alex Boag-Munroe
2023-09-22 17:28 ` Arthur Zamarin
2023-09-23 13:59 ` Sam James
2023-09-23 7:02 ` Ulrich Mueller
2023-09-23 13:54 ` Sam James
2023-09-23 14:01 ` Alex Boag-Munroe
2023-09-23 17:48 ` Ulrich Mueller
2023-09-24 18:29 ` Jonas Stein
2023-09-21 21:22 ` [gentoo-dev] " Ulrich Mueller
2023-09-21 22:10 ` Tim Harder
2023-09-21 22:19 ` Sam James
2023-09-22 3:54 ` Oskari Pirhonen [this message]
2023-09-22 12:12 ` Arthur Zamarin
2023-09-22 3:59 ` Oskari Pirhonen
2023-09-22 9:21 ` Ulrich Mueller
2023-09-22 9:53 ` Arthur Zamarin
2023-09-22 11:16 ` [gentoo-dev] " Florian Schmaus
2023-09-22 11:23 ` Jaco Kroon
2023-09-24 18:40 ` Jonas Stein
2023-09-25 12:03 ` Ulrich Mueller
2023-09-26 1:29 ` Oskari Pirhonen
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=ZQ0QEbojCfyZD1-w@dj3ntoo \
--to=xxc3ncoredxx@gmail.com \
--cc=arthurzam@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ulm@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