[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug#31076] gnurl 7.59.0
From: |
Ricardo Wurmus |
Subject: |
Re: [bug#31076] gnurl 7.59.0 |
Date: |
Mon, 09 Apr 2018 22:49:41 +0200 |
User-agent: |
mu4e 1.0; emacs 25.3.1 |
Nils Gillmann <address@hidden> writes:
>> I'm looking into switching gnurl to bmake + mk-config. I've already got the
>> tools on my side.
>> Do you want me to continue the native autotools support for Guix in gnurl,
>> derived from curl? Or would it be okay to switch guix over to bmake +
>> mk-config if it works out for gnurl?
>>
>> I'm asking because I could manage to support 2 build-system, it just would
>> be a bit unconvenient for me.
>
> Correction: I noticed this will make building gnurl unpleasant on guix side.
> I would have to introduce the bmake + mk + the bootstrapping of bmake without
> make in the build system I'm currently working on.. in Guix, which is
> something
> I'm pretty sure will not be taken into master.
>
> Alternative: a simple bmake using the gnu-build-system (and therefore
> depending
> on make deeper down the graph) would be accepted I guess?
What is the purpose of swapping out the build system? I thought gnurl
is not supposed to be a project in its own right, so making gratuitous
changes to the build system seems like it wouldn’t be in scope. It also
sounds like it would *add* dependencies purely for another build system,
even though a perfectly adequate build system already exists.
--
Ricardo