From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Cc: Ulrich Mueller <ulm@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: Mon, 2 Oct 2017 12:58:06 -0700 [thread overview]
Message-ID: <CAGfcS_n7TXL0s+uY5vYTiWdq4w8w6qeSZ5qPm2TCm=imFoRS+g@mail.gmail.com> (raw)
In-Reply-To: <d08be261-3447-3bb8-a9a8-ef7d396ed4c8@gentoo.org>
On Mon, Oct 2, 2017 at 12:33 PM, Kristian Fiskerstrand <k_f@gentoo.org> wrote:
> On 10/02/2017 09:25 PM, Ulrich Mueller wrote:
>> Here is again an item that was retracted from last month's agenda,
>> in modified form. This time, it only affects the syntax of dependency
>> groups but not their truth value:
>
> I might be misremembering, but wasn't the discussion going along the
> lines of this actually belonging in devmanual, and as such is more QA
> territory, if it doesn't affect the value the package manager evaluates to?
>
Does the PMS actually define what the correct behavior is for this
syntax? IMO a spec ought to do that, unless we really want to define
it as "undefined." (While rare that actually does come up for various
reasons.)
Now, if it is defined and we just need to communicate that we want our
devs to avoid it anyway, then that is QA territory. There are an
infinite number of ways to write a program that meets a spec, but that
doesn't mean that we want all of them showing up.
We could also make it a QA issue for now and then fix the spec in the
next PMS revision, and leave the behavior undefined going back.
--
Rich
next prev parent reply other threads:[~2017-10-02 19:58 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 [this message]
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
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_n7TXL0s+uY5vYTiWdq4w8w6qeSZ5qPm2TCm=imFoRS+g@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=council@gentoo.org \
--cc=gentoo-project@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