From: Nils Gillmann <ng0@n0.is>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, Nils Gillmann <ng0@n0.is>
Subject: Re: [bug#31076] gnurl 7.59.0
Date: Tue, 10 Apr 2018 09:41:53 +0000 [thread overview]
Message-ID: <20180410094153.sw5imlmxivd5gdw5@abyayala> (raw)
In-Reply-To: <87o9isnlzu.fsf@elephly.net>
Ricardo Wurmus transcribed 1.2K bytes:
>
> 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.
It is a project on its own for GNUnet and Taler. The amount of changes that went into
the build system specifically lead to merges being easy to make but an annoying pain
to check and merge.
Furthermore gnurl does not target the same obscure amount of platforms curl does, so
if I implement this, it will be just if it makes my life easier in the long run.
The fork in the code in gnurl from the beginning on was in the build-system of curl.
In theory I could revert my changes to the build system I made and maintain my own
set of build system files in the source, potentially decreasing merge time from now
around 15 - 120+ minutes to simply applying changes that happened in curl without
re-running my merge scripts.
> --
> Ricardo
>
>
prev parent reply other threads:[~2018-04-10 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 12:24 [bug#31076] gnurl 7.59.0 Nils Gillmann
2018-04-08 20:49 ` bug#31076: " Ludovic Courtès
2018-04-08 21:28 ` [bug#31076] " Nils Gillmann
2018-04-09 16:51 ` Nils Gillmann
2018-04-09 20:49 ` Ricardo Wurmus
2018-04-10 9:41 ` Nils Gillmann [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180410094153.sw5imlmxivd5gdw5@abyayala \
--to=ng0@n0.is \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.