unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Paul Jewell via <help-guix@gnu.org>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Stumpwm & using Lisp in guix - particularly quicklisp
Date: Sun, 25 Dec 2022 07:16:32 +0000	[thread overview]
Message-ID: <e4b746d4-b9fb-7ead-2ac9-314911171553@teulu.org> (raw)
In-Reply-To: <CAFHYt55OgQPdsnT3UFE6wzLA6BdJaHeZBmBC8M73vwyN6Z9LqA@mail.gmail.com>

Hi Felix,

Thanks for the response!

On 25/12/2022 04:29, Felix Lechner wrote:
> Hi Paul,
>
> On Sat, Dec 24, 2022 at 1:46 AM Paul Jewell via <help-guix@gnu.org> wrote:
>> I want to use the same configuration file under guix.
>> Unfortunately I run into a problem as when stumpwm starts, it complains
>> it can't find package "ql".
> I have used StumpWM with simple configurations. I used only CL modules
> that were declared as prerequisites to StumpWM as it is packaged in
> Guix.

I have now added the relevant quicklisp packages via guix in my system 
configuration file, and they are all loading correctly. I am still 
getting an error with SB-CLTL2 which didn't go away when I added 
sbcl-trivial-cltl2 to my configuration - I am still looking for this 
solution (i.e. - trying to identify which package I need to add to 
satisfy this requirement!).

> StumpWM probably cannot see the Quicklisp packages you installed in
> your home directory (and maybe also not those in your home profile)
> because Guix generally uses absolute paths to make prerequisites
> available to software like StumpWM.

That makes sense.

> It means you may have to jump through some hoops to use additional
> prerequisites in a configuration that is loaded dynamically. In the
> past, I have provided updated package definitions to myself for that
> purpose. This is an area with which I am not very familiar, but the
> restrictions you are experiencing make sense to me and also match my
> own experience.

I am keen to get my guix system into a state where I can adopt it fully 
on my laptop. I find the documentation quite terse though when it comes 
to explaining how guix does things. As a reference, I have no 
complaints, but when you start off I find it explains how to do 
something (often with several variants), but not why. Starting with 
someone else's configuration initially was probably more of a hindrance 
than a help, but I am past that now.

Once I get everything as I like it, I think I will make a patch to fill 
out the stumpwm section in the cookbook so others can find their way in 
more easily.

Best regards,
Paul




  reply	other threads:[~2022-12-25  7:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-24  9:45 Stumpwm & using Lisp in guix - particularly quicklisp Paul Jewell via
2022-12-24 21:20 ` Trev
2022-12-25  4:29 ` Felix Lechner via
2022-12-25  7:16   ` Paul Jewell via [this message]
2022-12-25  7:41 ` Trev
2022-12-25  8:05   ` Paul Jewell via
2022-12-25 18:39     ` Trev
2022-12-26 14:14     ` Paul Jewell 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=e4b746d4-b9fb-7ead-2ac9-314911171553@teulu.org \
    --to=help-guix@gnu.org \
    --cc=felix.lechner@lease-up.com \
    --cc=paul@teulu.org \
    /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).