From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 44736@debbugs.gnu.org
Subject: [bug#44736] [Shepherd PATCH] build: Add guix.scm helper file.
Date: Mon, 11 Jan 2021 13:36:38 +0100 [thread overview]
Message-ID: <87o8hvfy5l.fsf@gnu.org> (raw)
In-Reply-To: <20201119125244.3674-1-efraim@flashner.co.il> (Efraim Flashner's message of "Thu, 19 Nov 2020 14:52:44 +0200")
Hello!
Efraim Flashner <efraim@flashner.co.il> skribis:
> * build-aux/guix.scm: New file.
Could you (1) add a copyright header, and (2) add this file to
‘EXTRA_DIST’ in ‘Makefile.am’?
> +(define (keep-file? file stat)
> + (not (any (lambda (my-string)
> + (string-contains file my-string))
> + (list ".git" ".dir-locals.el" "build-aux"))))
FWIW, I’m never quite sure what to do here. In Guile-zstd, I wrote
something that works even from a tarball (not a Git checkout), but it’s
a bit verbose:
https://notabug.org/guile-zstd/guile-zstd/src/master/guix.scm
> +(define (build-from-git base)
> + (package
> + (inherit base)
> + (version (git-version (package-version base) "HEAD" %git-commit))
> + (source (local-file %source-dir
> + #:recursive? #t
> + #:select? keep-file?))
[…]
> +(list (build-from-git (specification->package "shepherd"))
> + (build-from-git (specification->package "guile2.2-shepherd"))
> + ;; This version FTBFS due to an import of '(ice-9 threads)' in modules/shepherd.scm
> + ;(build-from-git (specification->package "guile2.0-shepherd"))
> + )
Should it be a manifest instead, so that ‘guix build -f’ works?
The downside of returning several packages is that ‘guix environment -l
guix.scm’ won’t work.
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-01-11 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 12:52 [bug#44736] [Shepherd PATCH] build: Add guix.scm helper file Efraim Flashner
2021-01-11 12:36 ` Ludovic Courtès [this message]
2021-01-21 10:13 ` Efraim Flashner
2023-06-02 13:54 ` bug#44736: " 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=87o8hvfy5l.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=44736@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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).