2010-11-16 00:41:35 Alex Alexander napisał(a):
> On Mon, Nov 15, 2010 at 07:40:44PM +0100, Arfrever Frehtes Taifersar Arahesis
> wrote:
> > Some updates to my suggestion:
> > - Files would optionally end with "-${EAPI}" suffix.
> > - The following files would be affected:
> > package.mask
> >
On Mon, Nov 15, 2010 at 07:40:44PM +0100, Arfrever Frehtes Taifersar Arahesis
wrote:
> Some updates to my suggestion:
> - Files would optionally end with "-${EAPI}" suffix.
> - The following files would be affected:
> package.mask
> package.unmask
> package.keywords
> package.accep
2010-11-15 19:32:28 Zac Medico napisał(a):
> On 11/15/2010 10:23 AM, Arfrever Frehtes Taifersar Arahesis wrote:
> > 2010-11-03 06:18:01 Zac Medico napisał(a):
> >> When you need to use a new EAPI, why not just create a sub-profile that
> >> uses the existing 'eapi' file support? For example, you co
Some updates to my suggestion:
- Files would optionally end with "-${EAPI}" suffix.
- The following files would be affected:
package.mask
package.unmask
package.keywords
package.accept_keywords
package.use
package.provided
use.force
use.mask
use.unsatisfiable
On 11/15/2010 10:23 AM, Arfrever Frehtes Taifersar Arahesis wrote:
> 2010-11-03 06:18:01 Zac Medico napisał(a):
>> When you need to use a new EAPI, why not just create a sub-profile that
>> uses the existing 'eapi' file support? For example, you could create
>> 10.1 profiles that inherit from the 1
2010-11-03 06:18:01 Zac Medico napisał(a):
> When you need to use a new EAPI, why not just create a sub-profile that
> uses the existing 'eapi' file support? For example, you could create
> 10.1 profiles that inherit from the 10.0 profiles, and put anything
> requiring the new EAPI in the 10.1 sub-
On 11/01/2010 10:06 AM, Arfrever Frehtes Taifersar Arahesis wrote:
> I would like to suggest improvement in handling of EAPI in profiles:
> Some files could optionally end with ":${EAPI}", which would be used to
> specify, which EAPI
> should be used for parsing of given file. It would concern at
On 2010.11.01 17:06, Arfrever Frehtes Taifersar Arahesis wrote:
> I would like to suggest improvement in handling of EAPI in profiles:
> Some files could optionally end with ":${EAPI}",
[snip]
>
> --
> Arfrever Frehtes Taifersar Arahesis
>
Why does this remind me of GLEP55 ?
If we are going
On 01-11-2010 18:06:19 +0100, Arfrever Frehtes Taifersar Arahesis wrote:
> I would like to suggest improvement in handling of EAPI in profiles:
> Some files could optionally end with ":${EAPI}", which would be used to
> specify, which EAPI
Please don't use ':', neither any other special character
I would like to suggest improvement in handling of EAPI in profiles:
Some files could optionally end with ":${EAPI}", which would be used to
specify, which EAPI
should be used for parsing of given file. It would concern at least the
following files:
package.mask
package.use
use.force
use.
10 matches
Mail list logo
