From: Guillaume Le Vaillant <glv@posteo.net>
To: Charles <Charles.b.jackson@proton.me>
Cc: "59592@debbugs.gnu.org" <59592@debbugs.gnu.org>
Subject: [bug#59592] (No Subject)
Date: Sat, 28 Jan 2023 09:46:51 +0000 [thread overview]
Message-ID: <87h6wbarnx.fsf@kitej> (raw)
In-Reply-To: <LAXnBfDNwRRdjRJ5mlEzriczZoGm_z6BhmYTPTtE9iTzxQJWn-a1bcxy7zpKoy5z_yzroMXl_l-VzZ-h9HRH_vSYESOEjhfLVRj4ZklxkJM=@proton.me>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
Charles <Charles.b.jackson@proton.me> skribis:
> I didn't know that package-inferred-systems also coupled asdf systems in addition to packages and files. I'm not a fan of package-inferred-system if you couldn't tell.
>
> What are your thoughts on a patch that would add all systems to #:asd-systems?
> I could use your program along with some manual filtering to filter it out. It
> is ideal to have the knowledge of all asd-systems of a project before loading
> it.
Adding everything to 'asd-systems' would be tedious. I think Guix
package definitions are not the right place to keep the complete list of
available ASDF systems (just like we don't keep the list of ".so"
C libraries in package definitions).
There's a file search functionality that is being developped (there's
some info about it in the guix-devel mailing list I think). Maybe it
could be used as a base for a script searching for ASDF systems.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2023-01-28 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 4:09 [bug#59592] Keep asd-systems for cl-* packages Charles via Guix-patches via
2022-12-08 4:14 ` Charles via Guix-patches via
2023-01-10 13:05 ` Guillaume Le Vaillant
2023-01-20 20:24 ` [bug#59592] (No Subject) Charles via Guix-patches via
2023-01-28 9:46 ` Guillaume Le Vaillant [this message]
2023-01-28 16:23 ` Charles via Guix-patches via
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=87h6wbarnx.fsf@kitej \
--to=glv@posteo.net \
--cc=59592@debbugs.gnu.org \
--cc=Charles.b.jackson@proton.me \
/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).