From: Andy Patterson <ajpatter@uwaterloo.ca>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org, Toni Reina <areina@riseup.net>
Subject: Re: StumpWM package doesn't work
Date: Sat, 3 Dec 2016 23:11:56 -0500 [thread overview]
Message-ID: <20161203231157.24e4b6a0@uwaterloo.ca> (raw)
In-Reply-To: <87vav8dj94.fsf@gnu.org>
On Mon, 28 Nov 2016 10:53:16 +0100
ludo@gnu.org (Ludovic Courtès) wrote:
> Andy Patterson <ajpatter@uwaterloo.ca> skribis:
>
> > On Sun, 27 Nov 2016 21:43:23 +0100
> > ludo@gnu.org (Ludovic Courtès) wrote:
> >
> >> iyzsong@member.fsf.org (宋文武) skribis:
> >>
> >> > Toni Reina <areina@riseup.net> writes:
> >> >
> >> >> Hello,
> >> >>
> >> >> I'm trying to install `sbcl-stumpwm` package and looks like it
> >> >> doesn't work correctly. It's installed with no errors, but it
> >> >> doesn't generate the stumpwm binary file.
> >> >>
> >> >> The following package will be installed:
> >> >> sbcl-stumpwm
> >> >> 0.9.9 /gnu/store/z92ri0kgjdavkp7llav1db0dia44sbid-sbcl-stumpwm-0.9.9
> >> >>
> >> >> ls /gnu/store/z92ri0kgjdavkp7llav1db0dia44sbid-sbcl-stumpwm-0.9.9
> >> >> -> lib share
> >> >>
> >> >
> >> > It's in the "bin" output of sbcl-stumpwm package, you can get it
> >> > with:
> >> >
> >> > guix package -i sbcl-stumpwm:bin
> >>
> >> It might be clearer to have an “out” and a “lib” output (instead of
> >> “bin” and “out”). WDYT, Andy & 宋文武?
> >
> > I think that would basically shift the awkwardness from package
> > installation over to package development, since it would then be
> > required that all dependants of stumpwm use the lib output in the
> > inputs field (but only on sbcl? - since ecl binaries aren't
> > supported just yet).
>
> OK but there’s only one dependent:
>
> --8<---------------cut here---------------start------------->8---
> $ guix refresh -l sbcl-stumpwm
> A single dependent package: sbcl-stumpwm-with-slynk-0.9.9
> --8<---------------cut here---------------end--------------->8---
>
> So I think it would be preferable to do it the way I suggest, no?
>
Sure, I agree. Packages which have a program built are more likely to
be leaves, after all.
Since there haven't been other replies, I think we've reached a
consensus. I'll work to roll this into other updates in the Lisp
packaging area, and report back.
--
Andy
prev parent reply other threads:[~2016-12-04 4:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 0:48 StumpWM package doesn't work Toni Reina
2016-11-27 5:59 ` 宋文武
2016-11-27 17:13 ` Toni Reina
2016-11-27 20:43 ` Ludovic Courtès
2016-11-28 7:27 ` Andy Patterson
2016-11-28 9:53 ` Ludovic Courtès
2016-12-04 4:11 ` Andy Patterson [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=20161203231157.24e4b6a0@uwaterloo.ca \
--to=ajpatter@uwaterloo.ca \
--cc=areina@riseup.net \
--cc=help-guix@gnu.org \
--cc=ludo@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.
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.