unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Ricardo Wurmus <rekado@elephly.net>,
	Guillaume Le Vaillant <glv@posteo.net>
Cc: help-guix@gnu.org
Subject: Re: Problems with McCLIM (Common Lisp)
Date: Sat, 05 Sep 2020 08:57:26 +0200	[thread overview]
Message-ID: <87wo18zp61.fsf@ambrevar.xyz> (raw)
In-Reply-To: <877dt9fqh6.fsf@elephly.net>

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

Hi Ricardo,

Ricardo Wurmus <rekado@elephly.net> writes:

> But shouldn’t it then be propagated?  I had to guess that I might need
> to install it.  I think it should just be installed when installing
> McClim.

I guess so, but I've never used McClim myself.

> So, is this something we need to patch in all the asd files for McClim?
> Or is this something we should change in the build system?

Something to change in our build system.

> I’d like to play with McClim and all its applications to see if it would
> be worth doing something like this for Guile :)

Maybe.  Have you considered using GObject Introspection to build
full-fledged GTK apps in Guile?  I've heard of 2 Guile libraries for GI:
guile-gi and g-golf.

>> The "deliver-asd" operation has been fixed in recent versions of ASDF,
>> so maybe it would be possible to use it instead of our home-made
>> functions to create asd files for the bundles.
>>
>> Another approach could be not to use ASDF bundles at all, and just use
>> the regular compilation operation of ASDF, except the fasl files would
>> be put it "/gnu/store/..." instead of "$HOME/.cache/common-lisp/...",
>> and our asdf-build-system would indicate to ASDF where to search for the
>> files.

Good ideas.

In my opinion, the fasls (pre-built binaries) should go to their
respective package outputs.

Every Common Lisp package would then have its sources in "out", the SBCL
fasls in "sbcl", the ECL libs in "ecl", etc.

After all, the main benefit of compiling the fasls is to make sure our
package loads properly.

> I don’t know enough about Common Lisp to give a valuable comment here,
> but I’d very much like to be able to install Common Lisp things without
> having to do additional work post installation.  Using more “default”
> ways to install ASDF bundles perhaps would get us closer to a default
> experience.

We already have this if you install the cl- packages instead of the
sbcl- ones.  It should provide a smooth user experience.

Cheers!

-- 
Pierre Neidhardt
https://ambrevar.xyz/

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

  reply	other threads:[~2020-09-05  6:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13  2:43 Problems with McCLIM (Common Lisp) Ricardo Wurmus
2020-08-13  7:16 ` Pierre Neidhardt
2020-08-13  9:08   ` Guillaume Le Vaillant
2020-09-04 16:37     ` Ricardo Wurmus
2020-09-05  6:57       ` Pierre Neidhardt [this message]
2020-09-05  7:20         ` Ricardo Wurmus
2020-09-05  9:49           ` Guillaume Le Vaillant
2020-09-05 17:52         ` Konrad Hinsen
2020-09-06  7:07           ` Pierre Neidhardt
2020-09-11 14:19             ` Katherine Cox-Buday
2020-09-11 14:40               ` 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=87wo18zp61.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=glv@posteo.net \
    --cc=help-guix@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.
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).