unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Improve ASDF build system for Common Lisp libraries
Date: Sun, 13 Sep 2020 12:08:33 +0200	[thread overview]
Message-ID: <87v9gigfa6.fsf@yamatai> (raw)
In-Reply-To: <87pn6rtd1y.fsf@yamatai>

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]


Guillaume Le Vaillant <glv@posteo.net> skribis:

> Pierre Neidhardt <mail@ambrevar.xyz> skribis:
>
>> About Osicat: There are grovel left overs that could be removed.
>> The former build system used to do that automatically.  Maybe we can
>> restore this behaviour?
>
> The former build system deleted everything in 'lib/common-lisp/' except
> the bundle. We can't do that anymore because now the fasl files that we
> have to keep are in a directory tree whose structure we can't really
> predict. It depends how the sources are organized.
> Maybe we could just add a 'cleanup-left-overs' phase in the definition
> of the packages where some left-overs can be deleted.

Actually, it looks like the files generated by the groveler can't be
removed. When doing '(asdf:load-system "osicat")', if these files are
not there cffi tries to generate them (and fails because the directory
is read-only).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2020-09-13 10:09 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 [this message]
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
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=87v9gigfa6.fsf@yamatai \
    --to=glv@posteo.net \
    --cc=guix-devel@gnu.org \
    --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).