all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Allan Webber <cwebber@dustycloud.org>
To: James Richardson <james@jamestechnotes.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: stumpwm and common lisp modules
Date: Mon, 26 Sep 2016 03:35:48 -0500	[thread overview]
Message-ID: <87lgyf12jf.fsf@dustycloud.org> (raw)
In-Reply-To: <87fuopmdak.fsf@thor.jamestechnotes.com>

James Richardson writes:

> Andy Patterson writes:
>
>> On Thu, 22 Sep 2016 23:40:46 -0400
>> James Richardson <james@jamestechnotes.com> wrote:
>>
>>> Hello list,
>>> 
>>> I was attempting to make a package for stumpwm. I got as far as, oh it
>>> has a dependency on cl-ppcre (and a few other cl packages). Well it
>>> turns out that actually putting a lisp module in a guix package seems,
>>> well, non trivial. Does anyone else have an interest getting lisp
>>> packages into Guix?
>>> 
>>> 
>>
>> Hi James,
>>
>> I've been working on a build system for CL packages for some time now,
>> which works well enough to produce a working stumpwm package. It still
>> has some missing parts and design issues which I've been mulling over,
>> but if you're interested I could try to clean things up and post my
>> progress soon.
>>
>> What do you think?
>
> I would be very interested! I'm not really a lisp expert (yet), but I
> will help where I can.

I'm very much so interested in running stumpwm again... please do
continue! :)

      parent reply	other threads:[~2016-09-26  8:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-23  3:40 stumpwm and common lisp modules James Richardson
2016-09-23  4:39 ` Andy Patterson
2016-09-24 17:13   ` James Richardson
2016-09-24 18:45     ` Andy Patterson
2016-09-26  8:35     ` Christopher Allan Webber [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lgyf12jf.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=guix-devel@gnu.org \
    --cc=james@jamestechnotes.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.