Mark H Weaver writes:
> Christopher Baines writes:
>
>> Mark H Weaver writes:
>>> How is it more flexible than a "wip-*" branch on Savannah?
>>
>> I wouldn't use quite the same words as Léo, but from my perspective,
>> controlling access to particular branches (master, staging,
>> core-updates
Hi Léo,
Léo Le Bouter writes:
> The people that work on it now are Raghav and me, and Raghav does not
> have commit access yet, so that's the only way we can work and
> cooperate now. We don't have a choice.
Sorry, but that's simply false. You _do_ have a choice. You can do
what we've been doi
Dear,
How can I modify the flags that any program is compiled with within guix? That
is, I can allow in the gnu-build-system to modify it globally so that I can
add the build flags to any package, for example, add the flags -O2
-march=native -mtune=native so global as I already mentioned, so that
Tale as old as time: I was fed up with some software and instead of
patching it I created a workaround. But I think it could be genuinely
useful for some other folks too.
My main use case is gonna be opening new kakoune windows, but it should
be useful more generally as well.
https://git.sr.ht/~ra
Hi Ludo!
Ludovic Courtès writes:
> Hello!
>
> Ludovic Courtès skribis:
>
>> Ludovic Courtès skribis:
>>
>>> Over the last few days I’ve been head-down working on
>>> ‘wip-build-systems-gexp’, the mythical branch that brings gexps to build
>>> systems and packages, so we can say goodbye to
>>>
For reference, crossposting:
I pushed 00c67375b17f4a4cfad53399d1918f2e7eba2c7d to core-updates. Your
patch. Thank you for it. Let's watch for upstream zstd fix also.
I pushed 9feef62b73e284e106717a386624d6da90750a3d to master.
Ubuntu released a patch in the mean time, so while we couldnt make su
Hello!
On Mon, 2021-03-29 at 19:02 -0400, Mark H Weaver wrote:
> This sounds theoretical. Concretely, what needs do you have that
> aren't
> being met by Savannah?
Per-branch access control
> I don't understand this. It seems to me the opposite.
>
> If I want to contribute to this external 'w
Christopher Baines writes:
> Mark H Weaver writes:
>> How is it more flexible than a "wip-*" branch on Savannah?
>
> I wouldn't use quite the same words as Léo, but from my perspective,
> controlling access to particular branches (master, staging,
> core-updates, ...) on Savannah is a good thing
On Sun, 2021-03-28 at 16:48 -0400, Mark H Weaver wrote:
> How is it more flexible than a "wip-*" branch on Savannah?
>
> Thanks,
>Mark
Because as the GNU Guix project we have no control on the forge to
catter it to our own needs, because there is bureaucracy involved with
approving n
Hi Maxime,
Maxime Devos writes:
> On Sun, 2021-03-28 at 17:37 -0400, Mark H Weaver wrote:
>> One thing to be very careful about is to only use 'gtk-doc/stable',
>> 'dblatex/stable', and 'imagemagick/stable' in native-inputs, and
>> moreover to make sure that no references to these */stable packa
Mark H Weaver writes:
> Earlier, I wrote:
>> One thing to be very careful about is to only use 'gtk-doc/stable',
>> 'dblatex/stable', and 'imagemagick/stable' in native-inputs, and
>> moreover to make sure that no references to these */stable packages
>> remain in any package outputs.
>>
>> Of
Hello Guix!
If anyone is curious of the work or wants to participate, we are
working there:
https://git.guix-patches.cbaines.net/guix-patches/log/?h=wip-gnome-40
The branch is based on core-updates and we will rebase it every now and
then, as well as merging patches to official core-updates as
Mark H Weaver writes:
> Léo Le Bouter writes:
>
>> If anyone is curious of the work or wants to participate, we are
>> working there:
>> https://git.guix-patches.cbaines.net/guix-patches/log/?h=wip-gnome-40
>>
>> The branch is based on core-updates and we will rebase it every now and
>> then, a
Hello,
> Mathieu, what’s preventing us from doing armhf-linux builds again? We
> could use the OverDrives for that (with an upper bound though), along
> with the SBCs in machines-for-berlin.scm.
>
> That won’t be enough to keep up, so perhaps we’ll have to restrict
> armhf-linux builds to the “
14 matches
Mail list logo
