From: Nick <gentoo-lisp@njw.me.uk>
To: gentoo-lisp@lists.gentoo.org
Subject: [gentoo-lisp] Stumpwm emacs dependency
Date: Sun, 15 Nov 2009 05:51:19 +0000 [thread overview]
Message-ID: <20091115055119.GA28673@slinky.tiscali.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
Hi there,
I thought I'd try out the stumpwm ebuild in the lisp overlay today,
as I've been using ratpoison for ages and have been curious about
stumpwm, and the gentoo ebuild looks somewhat broken judging by bug
#221355
However I see due to your build inheriting elisp it effectively
depends on emacs. This seems like an odd dependency for a window
manager, and I wonder if it's possible / reasonable to remove it?
Thanks,
Nick
--
Please GPG encrypt email to me if you are able.
GPG : 0x04E4653F | 9732 D7C7 A441 D79E FDF0 94F6 1F48 5674 04E4 653F
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2009-11-15 5:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 5:51 Nick [this message]
2009-11-15 8:40 ` [gentoo-lisp] Stumpwm emacs dependency Ulrich Mueller
2009-11-15 15:19 ` Nick
2009-11-15 16:38 ` Stelian Ionescu
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=20091115055119.GA28673@slinky.tiscali.co.uk \
--to=gentoo-lisp@njw.me.uk \
--cc=gentoo-lisp@lists.gentoo.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