On 29 March 2017 at 13:30, Profpatsch wrote:
> On 17-03-25 11:47pm, Ertugrul Söylemez wrote:
>> >> Issue pulseSupport -> does it make sense to have a global 'enable
>> >> pulse for all packgages' config.pulseSupport = true flag?
>> >>
>> >> packages could be using: config.pulseSupport or false to
On 17-03-25 11:47pm, Ertugrul Söylemez wrote:
> >> Issue pulseSupport -> does it make sense to have a global 'enable
> >> pulse for all packgages' config.pulseSupport = true flag?
> >>
> >> packages could be using: config.pulseSupport or false to disable by
> >> default then.
> >
> > In my opinion
On Fri, 24 Mar, 2017 at 15:18:25 +, Marc Weber wrote:
> Gentoo use flags traditionally have been used to enable commonly used
> flags such as 'qt support' 'gtk support' or similar.
I like the idea, especially because it would help creating and using a
consistent naming scheme :)
Btw do we act
>> Issue pulseSupport -> does it make sense to have a global 'enable
>> pulse for all packgages' config.pulseSupport = true flag?
>>
>> packages could be using: config.pulseSupport or false to disable by
>> default then.
>
> In my opinion baking global implicit state into nixpkgs is not a good
> i
On 17-03-24 03:18pm, Marc Weber wrote:
> Issue pulseSupport -> does it make sense to have a global 'enable pulse
> for all packgages' config.pulseSupport = true flag?
>
> packages could be using: config.pulseSupport or false to disable by
> default then.
>
> Having a defaultFlags = {
> config.
Issue pulseSupport -> does it make sense to have a global 'enable pulse
for all packgages' config.pulseSupport = true flag?
packages could be using: config.pulseSupport or false to disable by
default then.
Gentoo use flags traditionally have been used to enable commonly used
flags such as 'qt su
