From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Improve ASDF build system for Common Lisp libraries
Date: Tue, 15 Sep 2020 09:12:24 -0500 [thread overview]
Message-ID: <87d02nyvqv.fsf@gmail.com> (raw)
In-Reply-To: <87sgbjwb5l.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 15 Sep 2020 13:07:50 +0200")
Ricardo Wurmus <rekado@elephly.net> writes:
> Pierre Neidhardt <mail@ambrevar.xyz> writes:
>
>> Some .asd definitions have dependencies (declared with
>> :system-depends-on).
>> A common dependency is prove-asdf.
>>
>> If we read all .asd then we must drag all ASDF dependencies. This can be a
>> burden, say, for a test system that is not supported in Guix at the moment.
>>
>> My intuition is that parsing all ASD files is a good default behaviour
>> but we should allow to override it with the asd-files keyword.
>
> Sounds good to me. When asd-files is provided we respect it, otherwise
> we’ll try to use them all.
+1 to allowing overrides for =asd-files=. If nothing else, packages need
to be flexible!
In addition to what Pierre is pointing out, the only issue I can think
of with reading in all asd files is perhaps source trees which vendor
packages. I don't think this is common in Common Lisp source trees, so
maybe that's something we can deal with if it comes up.
--
Katherine
next prev parent reply other threads:[~2020-09-15 14:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 9:36 Improve ASDF build system for Common Lisp libraries Guillaume Le Vaillant
2020-09-12 10:26 ` Pierre Neidhardt
2020-09-12 11:11 ` Pierre Neidhardt
2020-09-12 12:06 ` Guillaume Le Vaillant
2020-09-13 10:08 ` Guillaume Le Vaillant
2020-09-13 10:31 ` Pierre Neidhardt
2020-09-13 11:56 ` Guillaume Le Vaillant
2020-09-13 10:36 ` Pierre Neidhardt
2020-09-13 12:49 ` Guillaume Le Vaillant
2020-09-13 13:15 ` Pierre Neidhardt
2020-09-14 13:39 ` Guillaume Le Vaillant
2020-09-15 6:18 ` Pierre Neidhardt
2020-09-12 12:07 ` Pierre Neidhardt
2020-09-15 10:00 ` Guillaume Le Vaillant
2020-09-15 10:54 ` Pierre Neidhardt
2020-09-15 11:07 ` Ricardo Wurmus
2020-09-15 14:12 ` Katherine Cox-Buday [this message]
2020-09-15 16:28 ` Guillaume Le Vaillant
2020-09-17 9:45 ` Pierre Neidhardt
2020-09-23 11:15 ` Pierre Neidhardt
2020-09-23 12:44 ` Guillaume Le Vaillant
2020-09-23 13:35 ` Ricardo Wurmus
2020-09-23 13:41 ` Pierre Neidhardt
2020-09-12 15:35 ` Katherine Cox-Buday
2020-09-12 18:59 ` Konrad Hinsen
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=87d02nyvqv.fsf@gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).