From: Rich Freeman <rich0@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: Kristian Fiskerstrand <k_f@gentoo.org>,
gentoo-project <gentoo-project@lists.gentoo.org>,
Gentoo Council <council@gentoo.org>
Subject: Re: [gentoo-project] Re: [gentoo-dev-announce] Call for agenda items, council meeting 8/October/2017 18:00 UTC
Date: Tue, 3 Oct 2017 08:39:09 -0400 [thread overview]
Message-ID: <CAGfcS_m+_5zPFOxEaDQYhbsv0yD4QhzfsdTiNHTQ8TkH_QPYcg@mail.gmail.com> (raw)
In-Reply-To: <22995.28386.472489.467095@a1i15.kph.uni-mainz.de>
On Tue, Oct 3, 2017 at 7:05 AM, Ulrich Mueller <ulm@gentoo.org> wrote:
>
> In addition, Portage doesn't support empty groups since 2011. That for
> itself is not an argument to change PMS, but it shows that there is no
> need for the construct.
>
If the behavior of portage doesn't match the specification in PMS that
is reason enough to change one or the other. The purpose of PMS is to
document how package managers are supposed to behave.
You could:
1. Change portage to behave as PMS specifies.
2. Change PMS to specify portage's behavior.
3. Change PMS to make the behavior explicitly undefined.
Sure, this might be a lower-priority bug but this seems like a valid
one. What is the point in having a specification if we don't actually
specify what we're doing?
--
Rich
next prev parent reply other threads:[~2017-10-03 12:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 15:08 [gentoo-project] Call for agenda items, council meeting 8/October/2017 18:00 UTC Andreas K. Huettel
2017-09-26 18:58 ` Michał Górny
2017-09-27 19:24 ` Michał Górny
2017-09-28 9:06 ` Git workflow GLEP (Was: Re: [gentoo-project] Call for agenda items, council meeting 8/October/2017 18:00 UTC) Kristian Fiskerstrand
2017-09-28 19:46 ` Michał Górny
2017-09-28 19:56 ` Kristian Fiskerstrand
2017-09-28 20:17 ` Michał Górny
2017-09-29 12:45 ` Kristian Fiskerstrand
2017-09-30 17:32 ` Michał Górny
2017-09-30 17:36 ` Kristian Fiskerstrand
2017-09-30 18:48 ` Michał Górny
2017-10-01 20:37 ` Andreas K. Huettel
2017-10-02 12:01 ` Kristian Fiskerstrand
2017-09-29 13:10 ` Kristian Fiskerstrand
2017-10-01 20:41 ` [gentoo-project] Call for agenda items, council meeting 8/October/2017 18:00 UTC Andreas K. Huettel
2017-10-01 21:04 ` Michał Górny
2017-10-02 19:25 ` [gentoo-project] Re: [gentoo-dev-announce] " Ulrich Mueller
2017-10-02 19:33 ` Kristian Fiskerstrand
2017-10-02 19:58 ` Rich Freeman
2017-10-02 20:01 ` Kristian Fiskerstrand
2017-10-02 20:05 ` Michał Górny
2017-10-02 20:15 ` Rich Freeman
2017-10-03 11:05 ` Ulrich Mueller
2017-10-03 11:10 ` Kristian Fiskerstrand
2017-10-03 18:13 ` Michał Górny
2017-10-03 12:39 ` Rich Freeman [this message]
2017-10-03 16:57 ` Ulrich Mueller
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=CAGfcS_m+_5zPFOxEaDQYhbsv0yD4QhzfsdTiNHTQ8TkH_QPYcg@mail.gmail.com \
--to=rich0@gentoo.org \
--cc=council@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=k_f@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