unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Trev <trev@trevdev.ca>
To: Paul Jewell <paul@teulu.org>, "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Stumpwm & using Lisp in guix - particularly quicklisp
Date: Sat, 24 Dec 2022 23:41:54 -0800	[thread overview]
Message-ID: <87ili0ylod.fsf@guix.mail-host-address-is-not-set> (raw)
In-Reply-To: <f15ad0c6-6b01-2461-2b41-0fbefa12711d@teulu.org>

Paul Jewell via <help-guix@gnu.org> writes:

> Good morning Guix,
>
> I have a working stumpwm config which I use on my desktop gentoo 
> installation, and 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". Quicklisp is installed in my user home 
> directory, but this is clearly not being seen by stumpwm. I also note 
> that packages I can install through quicklisp are also packaged in guix 
> (e.g. alexandria). When I start sbcl in a terminal, everything works as 
> expected, and quicklisp is seen.
>
> This leads me to some questions:
>
>   * How do I configure stumpwm on my system so it looks in my home
>     directory, and observes my .sbclrc file when starting?
>   * What is the guix recommended way for working with lisp packages?
>     Should I avoid using quicklisp, and instead use the provided
>     packages in guix? I am unable to find any documentation (either
>     official or blog posts etc) explaining this.
>
> Many thanks!

I have no experience with quicklisp and am new to Common Lisp in
general, but I do use guix and am getting happier with every hack I make
on stumpwm and I can tell you what has worked for me:

1. Use the supported asdf system that Guix uses to package lisp programs
and extensions.

2. Install your stumpwm, repl & extensions in the same profile, be that
profile your system or your home/user space.  This helps a sbcl find
everything.

3. If you want some divergent profile to pick up all the bits from your
system or home profile, make sure to include them all in that divergent
profile.  An example of this is I used to have stumpwm in my root system
because I wanted GDM/convenience.  I then wanted all other related 3rd
party scripts to be contained in my home profile.  To make this work I
had to declare all the same dependencies in my home profile as I had my
root system.

The source code is your best friend for learning how to
package/implement the asdf build system.  You can also check the
documentation for build systems in general:
https://guix.gnu.org/manual/devel/en/html_node/Build-Systems.html

For the most part I have been able to find everything I needed from the
official guix repository.  I have contributed back the things I could
not find wherever it seemed appropriate.  For everything else, I have my
own personal guix channel.  I do this to avoid the need for activating
guix shell over and over again.

I get that quicklisp is an expected way to manage 3rd party packages for
Common Lisp but after years of working with NPM & JavaScript, the idea
of quicklisp turns me off.  Rant over, I hope this helped!

-- 

Trev : 0FB7 D06B 4A2A F07E AD5B  1169 183B 6306 8AA1 D206


  parent reply	other threads:[~2022-12-25  9:16 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
2022-12-25  7:41 ` Trev [this message]
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=87ili0ylod.fsf@guix.mail-host-address-is-not-set \
    --to=trev@trevdev.ca \
    --cc=help-guix@gnu.org \
    --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).