From: "Ludovic Courtès" <ludo@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 52422@debbugs.gnu.org
Subject: [bug#52422] [PATCH v2 1/2] gnu: Add bibutils.
Date: Fri, 24 Dec 2021 15:51:03 +0100 [thread overview]
Message-ID: <87ee62ukdk.fsf@gnu.org> (raw)
In-Reply-To: <4e416f3b4398e16d0e1d570689d50649d35cbc41.camel@gmail.com> (Liliana Marie Prikler's message of "Sat, 11 Dec 2021 08:43:10 +0100")
Hi,
Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:
> * gnu/packages/textutils.scm (bibutils): New variable.
> ---
> Am Mittwoch, dem 22.12.2021 um 22:42 +0100 schrieb Ludovic Courtès:
>> Bonus points if you change that to:
>>
>> (list #:configure-flags
>> #~(list … #$output …)
>> …)
> Watch my street cred go up as I mix quasiquote and gexp 😎
I try to avoid that because I’m think it can be quite confusing and
intimidating, especially when you end up with sequences like ,#~.
That’s a discussion we should have, but I’m in favor of the above style.
> On a related note, is it already known that you can't use
> (arguments #~(list ...))?
Yes, that’s because ‘arguments’ is literally a list of arguments passed
to the build system with ‘apply’.
>> GPLv2-only?
> Yes. They don't copypasta the full license blurb, but all file headers
> say that the source code is distributed under "GPL version 2".
V2-only then.
Thanks!
Ludo’.
next prev parent reply other threads:[~2021-12-24 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 7:43 [bug#52422] [PATCH] gnu: Add bibutils Liliana Marie Prikler
2021-12-11 7:43 ` [bug#52422] [PATCH v2 1/2] " Liliana Marie Prikler
2021-12-24 14:51 ` Ludovic Courtès [this message]
2021-12-24 18:14 ` bug#52422: " Liliana Marie Prikler
2021-12-22 21:42 ` [bug#52422] [PATCH] " Ludovic Courtès
2021-12-23 22:12 ` [bug#52422] [PATCH v2 2/2] gnu: Move go-github-com-aswinkarthik-csvdiff to textutils Liliana Marie Prikler
2021-12-24 14:52 ` Ludovic Courtès
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=87ee62ukdk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=52422@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
/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).