On Fri, 20 May 2016 13:34:37 -0400
Michael Orlitzky wrote:
> On 05/20/2016 12:48 PM, Michał Górny wrote:
> >
> > That's not a case since GLEP doesn't define how it is configured.
> > And it's invalid to reference other groups in path=s of a defined
> > group.
> >
>
> I'm just playing languag
On Fri, 20 May 2016 16:00:38 -0400
Ian Stakenvicius wrote:
> On 20/05/16 11:49 AM, Michał Górny wrote:
> > On Fri, 20 May 2016 11:40:39 -0400
> > Michael Orlitzky wrote:
> >
> >> On 05/20/2016 11:34 AM, Daniel Campbell wrote:
> >>>
> >>> ...and the user has this in their install.mask file:
On 20/05/16 11:49 AM, Michał Górny wrote:
> On Fri, 20 May 2016 11:40:39 -0400
> Michael Orlitzky wrote:
>
>> On 05/20/2016 11:34 AM, Daniel Campbell wrote:
>>>
>>> ...and the user has this in their install.mask file:
>>>
>>> [bash-completion]
>>> path=/some/other/path
>>> desc=some other descrip
On 05/20/2016 12:48 PM, Michał Górny wrote:
>
> That's not a case since GLEP doesn't define how it is configured.
> And it's invalid to reference other groups in path=s of a defined
> group.
>
I'm just playing language lawyer. The spec does say,
A Package Manager implementing this specificati
On Fri, 20 May 2016 12:15:36 -0400
Michael Orlitzky wrote:
> On 05/20/2016 11:44 AM, Michał Górny wrote:
> >
> > I'd make '@' signify group names, like we do for sets. This would have
> > the side limitation that it would make it impossible to filter
> > filenames starting with '@' with the curr
On 05/20/2016 11:44 AM, Michał Górny wrote:
>
> I'd make '@' signify group names, like we do for sets. This would have
> the side limitation that it would make it impossible to filter
> filenames starting with '@' with the currently supported
> path-or-filename syntax.
>
That may be the best we
On Fri, 20 May 2016 11:40:39 -0400
Michael Orlitzky wrote:
> On 05/20/2016 11:34 AM, Daniel Campbell wrote:
> >
> > ...and the user has this in their install.mask file:
> >
> > [bash-completion]
> > path=/some/other/path
> > desc=some other description
> >
>
> I don't think that's allowed; th
On Fri, 20 May 2016 11:30:59 -0400
Michael Orlitzky wrote:
> On 05/20/2016 11:21 AM, Michał Górny wrote:
> >
> > ...
> >
> > Getting into implementation details, I'd probably go for:
> >
> > INSTALL_MASK="@bash-completion"
> >
> > but the exact syntax is left for various package managers. P
On 05/20/2016 11:34 AM, Daniel Campbell wrote:
>
> ...and the user has this in their install.mask file:
>
> [bash-completion]
> path=/some/other/path
> desc=some other description
>
I don't think that's allowed; the groups are specified by each
repository's metadata/install-mask.conf, not by th
On 05/20/2016 07:01 AM, Michał Górny wrote:
> Hello,
>
> Sometime around a year ago, I started working on extending INSTALL_MASK
> to support well-defined locations. The work was never finished, and I
> just found my old specification for it. I've cleaned it up a bit,
> and extended it into a comp
On 05/20/2016 11:21 AM, Michał Górny wrote:
>
> ...
>
> Getting into implementation details, I'd probably go for:
>
> INSTALL_MASK="@bash-completion"
>
> but the exact syntax is left for various package managers. Paludis
> and pkgcore would probably prefer a proper configuration file.
>
Ok,
On Fri, 20 May 2016 11:12:02 -0400
Michael Orlitzky wrote:
> On 05/20/2016 10:01 AM, Michał Górny wrote:
> >
> > Please review the specification provided. The basic goal is to provide
> > an ability to use INSTALL_MASK alike USE flags -- with path groups that
> > are well-defined and described i
On 05/20/2016 10:01 AM, Michał Górny wrote:
>
> Please review the specification provided. The basic goal is to provide
> an ability to use INSTALL_MASK alike USE flags -- with path groups that
> are well-defined and described in the repository.
>
> [1]:https://wiki.gentoo.org/wiki/User:MGorny/GLE
13 matches
Mail list logo
