From: Charles <Charles.b.jackson@proton.me>
To: Guix Devel <guix-devel@gnu.org>
Subject: Package Argument #:asd-systems Missing & Guix Provides
Date: Wed, 16 Nov 2022 20:55:45 +0000 [thread overview]
Message-ID: <VlISzC3ErnExP42qmP5p7A-NWGQ9vL3OsVvX5gmqGFHDCzrIjh43D-2obRYlTi3_SmFbTk5e7iisshOqtVd_h7UG24Jq6E5riZvlNba22O8=@proton.me> (raw)
Hello Guix Developers.
More specifically, the #:asd-systems package-argument is missing from lisp libraries using the asdf-build-system/source (packages like cl-alexandria). I understand that it is removed on line 205 of guix/build-system/asdf.scm along with other package-arguments.
(strip-keyword-arguments
'(#:tests? #:lisp #:asd-systems #:asd-test-systems #:asd-operation)
(package-arguments pkg))
The reason is clear: asdf-build-system/source doesn't actually build anyting, so it doesn't need any build arguments. Would it hurt to leave the package-arguments there even though they are unused?
Full Context:
I am trying to make a guix-provides script that would take some artifact (name of asd-system) as input and give the packages that create those artifacts.
Examples:
Find by asdf-system
$ guix provides --asdf-system com.inuoe.jzon
sbcl-jzon
ecl-jzon
cl-jzon
Find by binary. I think it will take significant changes to get this one to work.
$ guix provides as
binutils
I'm working on the --asdf-system version as a proof of concept because I like lisp, and it seems doable with minimal changes. The one problem I'm running into is not having access to the #:asd-systems package argument for packages with asdf-build-system/source. I agin ask: Would it be possible to leave the package-arguments (at least the #:asd-systems) in tact for asdf-build-system/source packages?
- Charles
next reply other threads:[~2022-11-16 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 20:55 Charles [this message]
2022-11-18 14:19 ` Package Argument #:asd-systems Missing & Guix Provides Guillaume Le Vaillant
2022-11-18 16:38 ` Charles
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='VlISzC3ErnExP42qmP5p7A-NWGQ9vL3OsVvX5gmqGFHDCzrIjh43D-2obRYlTi3_SmFbTk5e7iisshOqtVd_h7UG24Jq6E5riZvlNba22O8=@proton.me' \
--to=charles.b.jackson@proton.me \
--cc=guix-devel@gnu.org \
/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).