From: Jack Hill <jackhill@jackhill.us>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: New build system: copy-build-system
Date: Sun, 26 Jan 2020 23:14:44 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.20.2001262311570.11123@marsh.hcoop.net> (raw)
In-Reply-To: <71f1c314039928365360de9345cbd2170100e093.camel@gmail.com>
On Sun, 26 Jan 2020, Jesse Gibbons wrote:
> On Sun, 2020-01-26 at 21:27 +0100, Pierre Neidhardt wrote:
>> Error verifying signature: Failed to execute gpg.
>> Hi!
>>
>> We've got quite a few packages that simply copy some files from their
>> source to the output. Examples include `debian-archive-keyring`,
>> `0ad-data`, `gcide`, or `rofi-pass`.
>>
>> Those packages end up being tedious to write because we need to rely
>> on
>> the trivial-build-system, also known as "the least trivial of them
>> all!" :)
>>
>> What about adding a "copy-build-system" which has one argument, say
>> an
>> `#:install-plan` that takes a list of source-destination pairs?
>>
>> This would drastically simplify the definition of the aforementioned
>> packages, basically summing up dozens of boilerplate lines into an
>> effectively trivial file mapping.
>>
>> If this sounds like a good idea, I'd be happy to send a patch!
>>
>> Cheers!
>>
> That would be great!
I agree that this would be great as well. In addition to tedium,
trivial-build-system can make modifications to package definitions, which
I consider a really cool guix feature and a win for software freedom,
more tricky. See
https://lists.gnu.org/archive/html/help-guix/2019-12/msg00139.html for an
issue I had with it (sorry Marius, I haven't had time to play with
switching the build system of matcha-theme, but it's still on my todo list
:)).
Best,
Jack
next prev parent reply other threads:[~2020-01-27 4:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-26 20:27 New build system: copy-build-system Pierre Neidhardt
2020-01-27 0:45 ` Jesse Gibbons
2020-01-27 4:14 ` Jack Hill [this message]
2020-01-27 14:27 ` zimoun
2020-01-27 14:44 ` Pierre Neidhardt
2020-01-27 15:03 ` zimoun
2020-01-27 15:18 ` Pierre Neidhardt
2020-01-27 15:36 ` zimoun
2020-01-27 15:51 ` Pierre Neidhardt
2020-01-27 16:17 ` zimoun
2020-01-27 18:18 ` Julien Lepiller
2020-01-27 16:45 ` How to deal with very large sources Ricardo Wurmus
2020-01-27 19:03 ` New build system: copy-build-system Ricardo Wurmus
2020-01-28 10:32 ` Ludovic Courtès
2020-01-28 13:39 ` Pierre Neidhardt
2020-01-28 23:04 ` Ludovic Courtès
2020-02-14 12:54 ` Pierre Neidhardt
2020-02-14 13:22 ` Julien Lepiller
2020-02-17 3:46 ` Jesse Gibbons
2020-02-17 7:56 ` Pierre Neidhardt
2020-02-17 16:52 ` Jesse Gibbons
2020-02-17 17:10 ` Pierre Neidhardt
2020-02-19 1:33 ` Alex Griffin
2020-02-19 14:01 ` Pierre Neidhardt
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=alpine.DEB.2.20.2001262311570.11123@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=guix-devel@gnu.org \
--cc=jgibbons2357@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).