On Fri, Sep 16, 2011 at 8:14 AM, Michał Górny wrote:
> On Fri, 16 Sep 2011 08:39:48 -0500
> Donnie Berkholz wrote:
>
>> On 11:36 Fri 16 Sep , Michał Górny wrote:
>> > The question is: where to store such a directory list?
>> >
>> > Keeping it inside project sources doesn't seem right as it wo
On Fri, 16 Sep 2011 11:42:59 -0400
Mike Frysinger wrote:
> On Friday, September 16, 2011 11:14:28 Michał Górny wrote:
> > On Fri, 16 Sep 2011 08:39:48 -0500 Donnie Berkholz wrote:
> > > I don't want this in my repo.
> >
> > By *your* repo you mean dev overlay? Noone forces you to declare
> > add
On Friday, September 16, 2011 11:14:28 Michał Górny wrote:
> On Fri, 16 Sep 2011 08:39:48 -0500 Donnie Berkholz wrote:
> > I don't want this in my repo.
>
> By *your* repo you mean dev overlay? Noone forces you to declare
> additional paths.
i think he meant maintaining masks for pkgs in his repo
On Fri, 16 Sep 2011 08:39:48 -0500
Donnie Berkholz wrote:
> On 11:36 Fri 16 Sep , Michał Górny wrote:
> > The question is: where to store such a directory list?
> >
> > Keeping it inside project sources doesn't seem right as it would
> > require me to bump and re-release project every time
On 11:36 Fri 16 Sep , Michał Górny wrote:
> The question is: where to store such a directory list?
>
> Keeping it inside project sources doesn't seem right as it would
> require me to bump and re-release project every time a directory is
> added. Keeping it in separate package which would ne
Hello,
I'm working on a tiny project called install-mask[1] which is
supposedly a simple tool to enable/disable INSTALL_MASK.
One of its features would be a common list of named locations where
users may really want to consider INSTALL_MASK-ing; in a way similar to
USE flags (or even instead of r
