From: Markos Chandras <hwoarang@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 19:40:09 +0000 [thread overview]
Message-ID: <52DD7B99.3080102@gentoo.org> (raw)
In-Reply-To: <20140120185426.GA6386@laptop.home>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 01/20/2014 06:54 PM, William Hubbs wrote:
> 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
>
There is no profiles.desc documentation in devmanual
http://devmanual.gentoo.org/profiles/profiles.desc/index.html
Discussing this in gentoo-dev makes no sense. Whoever wants the
profiles.desc to be part of the devmanual document, please submit a patch.
- --
Regards,
Markos Chandras
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQJ8BAEBCgBmBQJS3XuZXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzNTVDNDczOUYzRjJEMTRGNDRGMzU2RkMw
OUJGNEY1NEMyQkE3RjNDAAoJEAm/T1TCun88kzUP/iWTI2ee92duV80WfQh3O9Lj
Mkl4jFuTNmWqrMQfcO5Z3k+cSwTcxP5BI3IkmeD38obeGK+08hHBO16X/+6YQfWi
MDgmx3LOJPxxPo9Bi/LJ7DnBI2dLF8TbSWNTa/xuvHjfFC554BlesgY/tbsulVT+
cKMujknXvt4WbkyWSkddHeCcgsVYS9iR+zp7JkKLuJyx+D4Kj3xIXkaaVt+V0fS9
5FsRI+dWRCTAtyUU7hJ2T7R0o8opcO850xai/921lwIwSmD+uN9vVovKBKUPtiqH
SOEZkcpnCl9mLtdrmlUjsJFtosLHLAHDA9CADcnmCDxPFx4HEhSFWP35qGu17evk
YPyE5hQXKIFsgXPJm8GCVKWJfw5IgZH9WCF+Go+nHgxcnNEGQJKp81N5g3JAVeFu
Q2OjxEjqjy/LKdBDUUmOhiUs7yGL2YYVIzRnDy9O92Zb77PJqmlner+AWwHS9Oso
w0+1S8Q9n0SmJ641Md6FboqSfhQbm1IUB7GoGm9iuF5KDzglpZdiB6jhr82ApOKt
61opKYQSBeaSeognYt7pK45Nwp1C3UUmgEDQtoxukegV+OlB/ocCFN8nLWgLj0Dw
X/Me1iLUFXR/KF7TG+KQLSxJt6ftsAXmCXWQYKdfTEIEUmLsMpEjQWLhPYmZEMm4
6YdOvzo2V4Br8oo82pOQ
=UwDV
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-01-20 19:41 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
2014-01-20 19:40 ` Markos Chandras [this message]
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=52DD7B99.3080102@gentoo.org \
--to=hwoarang@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