From: Ricardo Wurmus <rekado@elephly.net>
To: Nils Gillmann <ng0@n0.is>
Cc: guix-devel@gnu.org
Subject: Re: [bug#31076] gnurl 7.59.0
Date: Mon, 09 Apr 2018 22:49:41 +0200 [thread overview]
Message-ID: <87o9isnlzu.fsf@elephly.net> (raw)
In-Reply-To: <20180409165122.p64efbsgksbywnqr@abyayala>
Nils Gillmann <ng0@n0.is> 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
next prev parent reply other threads:[~2018-04-09 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180406122457.dg5mvmgmuotfslho@abyayala>
[not found] ` <87po39todl.fsf@gnu.org>
2018-04-08 21:28 ` [bug#31076] gnurl 7.59.0 Nils Gillmann
2018-04-09 16:51 ` Nils Gillmann
2018-04-09 20:49 ` Ricardo Wurmus [this message]
2018-04-10 9:41 ` Nils Gillmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o9isnlzu.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ng0@n0.is \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).