From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Pierre Neidhardt <mail@ambrevar.xyz>, 56334@debbugs.gnu.org
Cc: glv@posteo.net
Subject: bug#56334: Should asdf-build-system/sbcl use load-system instead of compile-system?
Date: Fri, 01 Jul 2022 16:30:10 +0200 [thread overview]
Message-ID: <c65487060149d53a70d13cdfb50332b68ac440a6.camel@ist.tugraz.at> (raw)
In-Reply-To: <87edz5jfxm.fsf@ambrevar.xyz>
Am Freitag, dem 01.07.2022 um 12:16 +0200 schrieb Pierre Neidhardt:
> [...]
>
> From the ASDF doc:
>
> --8<---------------cut here---------------start------------->8---
> This will make sure all the files in the system are compiled, but not
> necessarily load any of them in the current image; on most systems,
> it will _not_ load all compiled files in the current image. This
> function exists for symmetry with 'load-system' but is not
> recommended *unless you are writing build scripts* and know what
> you're doing.
> --8<---------------cut here---------------end--------------->8---
>
> So should we really use it?
In this case, I'd argue that we *are* the build script and that
packagers know what they're doing when they override build in case that
asdf:compile-system fails. Unless I'm wrong, we're not actually
interested in loading all compiled files into the current image, are
we?
Cheers
next prev parent reply other threads:[~2022-07-01 14:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 10:16 bug#56334: Should asdf-build-system/sbcl use load-system instead of compile-system? Pierre Neidhardt
2022-07-01 11:13 ` Guillaume Le Vaillant
2022-07-01 11:45 ` Pierre Neidhardt
2022-07-01 12:22 ` Guillaume Le Vaillant
2022-07-01 14:46 ` Pierre Neidhardt
2022-07-01 16:40 ` Guillaume Le Vaillant
2022-07-01 17:07 ` Pierre Neidhardt
2022-07-02 10:17 ` Pierre Neidhardt
2022-07-03 10:19 ` Guillaume Le Vaillant
2022-07-04 15:18 ` Pierre Neidhardt
2022-07-04 19:57 ` Pierre Neidhardt
2022-07-05 8:56 ` Pierre Neidhardt
2022-07-17 16:19 ` Pierre Neidhardt
2022-08-03 14:49 ` Guillaume Le Vaillant
2022-08-04 14:01 ` Pierre Neidhardt
2022-07-01 14:30 ` Liliana Marie Prikler [this message]
2022-07-01 14:43 ` 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=c65487060149d53a70d13cdfb50332b68ac440a6.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=56334@debbugs.gnu.org \
--cc=glv@posteo.net \
--cc=mail@ambrevar.xyz \
/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).