From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] new profiles.desc header documenting profile/keyword policy
Date: Mon, 20 Jan 2014 12:54:26 -0600 [thread overview]
Message-ID: <20140120185426.GA6386@laptop.home> (raw)
In-Reply-To: <52DD6886.6000507@plaimi.net>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
On Mon, Jan 20, 2014 at 07:18:46PM +0100, Alexander Berntsen wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 20/01/14 18:26, William Hubbs wrote:
> > On Mon, Jan 20, 2014 at 02:23:24AM -0500, Mike Frysinger wrote:
> >> this has all been fairly ad-hoc in the past, so formalize it in
> >> the one place that impacts everyone -- profiles.desc.
> > If it is policy, shouldn't it go in the dev manual rather than in
> > this file?
> profiles.desc is installed on a user's system. Users don't read the
> dev manual.
All policies are being documented in the dev manual, so I was just
saying that I think this should go there if it is going to be official.
Whether or not it is in a local file (on the users' system) isn't
relevant, developers should be familiar with the dev manual.
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-01-20 18:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 7:23 [gentoo-dev] new profiles.desc header documenting profile/keyword policy Mike Frysinger
2014-01-20 17:26 ` William Hubbs
2014-01-20 18:18 ` Alexander Berntsen
2014-01-20 18:54 ` William Hubbs [this message]
2014-01-20 19:40 ` Markos Chandras
2014-01-21 15:10 ` Tom Wijsman
2014-01-22 6:58 ` Mike Frysinger
2014-01-21 15:05 ` Tom Wijsman
2014-01-22 6:58 ` Mike Frysinger
2014-01-22 23:51 ` Tom Wijsman
2014-01-25 13:35 ` Markos Chandras
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=20140120185426.GA6386@laptop.home \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.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