From: Pierre Neidhardt <mail@ambrevar.xyz>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: New build system: copy-build-system
Date: Mon, 27 Jan 2020 16:18:15 +0100 [thread overview]
Message-ID: <87k15dapxk.fsf@ambrevar.xyz> (raw)
In-Reply-To: <CAJ3okZ0XfiFf5KVV4DWRt-ROBe_GMv=yOSKmJZKmq=UOTNspQw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1530 bytes --]
zimoun <zimon.toutoune@gmail.com> writes:
> You want something like that:
>
> --8<---------------cut here---------------start------------->8---
> (define-public debian-archive-keyring
> (package
> (name "debian-archive-keyring")
> (version "2019.1")
> (source ...)
> (build-system copy-build-system)
> (arguments
> '(#:install-plan
> (lambda* (#:key outputs #:allow-other-keys)
> (let* ((out (assoc-ref outputs "out"))
> (apt (string-append out "/etc/apt/trusted.gpg.d/"))
> (key (string-append out "/share/keyrings/")))
> (install-file "keyrings/debian-archive-keyring.gpg" key)
> (install-file "keyrings/debian-archive-removed-keys.gpg" key)
> (for-each (lambda (file)
> (install-file file apt))
> (find-files "trusted.gpg" "\\.gpg$")))
> #t)))))
> --8<---------------cut here---------------end--------------->8---
Actually we could simplify the install plan with something like
--8<---------------cut here---------------start------------->8---
#:install-plan
(("source1" "target1")
("source-dir2/" "target-dir2" #:exclude ("foo")))
--8<---------------cut here---------------end--------------->8---
Regarding the data fetching, if I understand your point I think it
should be handled in a separate issue.
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-01-27 15:18 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
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 [this message]
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=87k15dapxk.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@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).