Re: [gentoo-dev] new profiles.desc header documenting profile/keyword policy

2014-01-25 Thread Markos Chandras
On 01/22/2014 06:58 AM, Mike Frysinger wrote: On Monday 20 January 2014 12:26:13 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

Re: [gentoo-dev] new profiles.desc header documenting profile/keyword policy

2014-01-22 Thread Tom Wijsman
On Wed, 22 Jan 2014 01:58:04 -0500 Mike Frysinger vap...@gentoo.org wrote: On Monday 20 January 2014 12:26:13 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

Re: [gentoo-dev] new profiles.desc header documenting profile/keyword policy

2014-01-21 Thread Tom Wijsman
On Mon, 20 Jan 2014 11:26:13 -0600 William Hubbs willi...@gentoo.org wrote: If it is policy, shouldn't it go in the dev manual rather than in this file? From a QA perspective, it would be nice to have the policy documentation available in both locations; but as duplication would create out of

Re: [gentoo-dev] new profiles.desc header documenting profile/keyword policy

2014-01-21 Thread Tom Wijsman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 20 Jan 2014 19:40:09 + Markos Chandras hwoar...@gentoo.org wrote: Discussing this in gentoo-dev makes no sense. Whoever wants the profiles.desc to be part of the devmanual document, please submit a patch. This confuses me, as vapier

Re: [gentoo-dev] new profiles.desc header documenting profile/keyword policy

2014-01-21 Thread Mike Frysinger
On Monday 20 January 2014 12:26:13 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

Re: [gentoo-dev] new profiles.desc header documenting profile/keyword policy

2014-01-21 Thread Mike Frysinger
On Monday 20 January 2014 13:18:46 Alexander Berntsen wrote: 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

Re: [gentoo-dev] new profiles.desc header documenting profile/keyword policy

2014-01-20 Thread William Hubbs
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. -mike If it is policy, shouldn't it go in the dev manual rather than in this file? Given that, I have

Re: [gentoo-dev] new profiles.desc header documenting profile/keyword policy

2014-01-20 Thread Alexander Berntsen
-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,

Re: [gentoo-dev] new profiles.desc header documenting profile/keyword policy

2014-01-20 Thread William Hubbs
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

Re: [gentoo-dev] new profiles.desc header documenting profile/keyword policy

2014-01-20 Thread Markos Chandras
-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,

[gentoo-dev] new profiles.desc header documenting profile/keyword policy

2014-01-19 Thread Mike Frysinger
this has all been fairly ad-hoc in the past, so formalize it in the one place that impacts everyone -- profiles.desc. -mike ### # This is a list of valid profiles for each architecture. This file is used by # repoman