unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Wil deBeest <bovid-19@4tii.de>
Cc: Benjamin Slade <beoram@gmail.com>,  help-guix@gnu.org
Subject: Re: stumpwm on guix - "sb-cltl2" issues
Date: Fri, 06 May 2022 09:44:46 -0500	[thread overview]
Message-ID: <87pmkqwwip.fsf@gmail.com> (raw)
In-Reply-To: <8840696C-4023-4DCD-9CDE-21A7FAED3AD1@4tii.de> (Wil deBeest's message of "Tue, 3 May 2022 16:35:49 +0200")

Wil deBeest <bovid-19@4tii.de> writes:

> 
> Wil deBeest <bovid-19@4tii.de> writes:
>
>> 
>> Benjamin Slade <beoram@gmail.com> writes:
>> 
>>> I'm trying to run my long-standing stumpwm init.lisp on a recent Guix
>>> install, using the packaged stumpwm, however when it launches, it
>>> fails to process the init.lisp and gives me an "Don't know how to
>>> REQUIRE sb-cltl2." error.
>>> I've set the SBCL_HOME variable both in .xprofile and in the init.lisp
>>> itself [via `(sb-posix:putenv
>>> "SBCL_HOME=/run/current-system/profile/lib/sbcl/")' ], but this
>>> doesn't seem to help.
>>> Is there a good way around this? (On my other system I just compile
>>> stumpwm from source and install; I don't know if that makes a
>>> difference here.)
>>> —Ben
>> 
>> I used to have the same problem, but I don't remember what fixed it.
>> 
>> SBCL_HOME isn't set at all, I only have `exec /home/bovid-19/.guix-profile/bin/stumpwm' in my
>> `~/.xinitrc', and my stumpwm init file starts like this:
>> 
>> (in-package :stumpwm)
>> (require 'sb-cltl2)
>> 
>> 
>> I'm not sure what else I can look for.
>
> I have probably found the solution: in addition to stumpwm, I also have
> `cl-trivial-cltl2' and `cl-asdf' (and sbcl) in my system configuration.
> If you can confirm that those two packages are what was missing, we
> should add them to the stumpwm package as inputs.

I think I have this problem? But like Benjamin, it has also been a very long time since I addressed it. In my profiles, I include:

                 "stumpwm"
                 "sbcl-stumpwm-kbd-layouts"
                 ;; net module has this unacknowledged dependency
                 "sbcl-cl-ppcre"
                 "sbcl-stumpwm-net"
                 "sbcl-stumpwm-pass"
                 "sbcl-stumpwm-stumptray"
                 "sbcl-stumpwm-swm-gaps"
                 "sbcl-stumpwm-ttf-fonts"

and I don't seem to have any problem. I start it from lightdm, and I don't think that's doing anything special.

Probably in my case some of the modules are including the missing dependencies.

I hope that helps somehow.

-- 
Katherine


  reply	other threads:[~2022-05-06 14:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 14:35 stumpwm on guix - "sb-cltl2" issues Wil deBeest
2022-05-06 14:44 ` Katherine Cox-Buday [this message]
2022-05-13 19:09   ` Benjamin Slade
2022-07-03  1:31     ` Benjamin Slade
  -- strict thread matches above, loose matches on Subject: below --
2022-05-03 14:18 Wil deBeest
2022-04-16  0:29 Benjamin Slade
2022-04-16 17:40 ` Guillaume Le Vaillant

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=87pmkqwwip.fsf@gmail.com \
    --to=cox.katherine.e@gmail.com \
    --cc=beoram@gmail.com \
    --cc=bovid-19@4tii.de \
    --cc=help-guix@gnu.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).