all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Christopher Baines <mail@cbaines.net>
Cc: 28886@debbugs.gnu.org
Subject: [bug#28886] [PATCH] gnu: Add emacs-robe.
Date: Mon, 04 Dec 2017 00:04:02 +0100	[thread overview]
Message-ID: <87374r4dnh.fsf@elephly.net> (raw)
In-Reply-To: <87h8uw42qi.fsf@elephly.net>

Hi again,

some time ago I wrote this:

Ricardo Wurmus <rekado@elephly.net> writes:

> Hi,
>
>> * gnu/packages/emacs.scm (emacs-robe): New variable.
>> ---
>
> Thanks, this looks good.
>
> The website lists a couple of Ruby dependencies:
>
> --8<---------------cut here---------------start------------->8---
> * pry
> * pry-doc >= 0.6.0 (on MRI)
> * method_source >= 0.8.2 (for compatibility with the latest
>  Rubinius)
> --8<---------------cut here---------------end--------------->8---
>
> yet, I don’t see them among the inputs of this package.  Is this just
> something that users are reasonably expected to have on their systems
> when they want to use robe, or should these things be among the inputs?
>
> I trust you made the right decision here, but I thought I’d just ask as
> it is a bit confusing.

“pry” is a ruby debugger, right?  It is a runtime dependency, but one
would expect a Ruby developer to provide one version or another,
dependent on their project.

If this is correct I don’t want to block this patch: it looks good to
me.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2017-12-04  2:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18  6:20 [bug#28886] [PATCH] gnu: Add emacs-robe Christopher Baines
2017-10-18 20:31 ` Ricardo Wurmus
2017-12-03 23:04   ` Ricardo Wurmus [this message]
2017-12-09 21:14     ` bug#28886: " Christopher Baines

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=87374r4dnh.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=28886@debbugs.gnu.org \
    --cc=mail@cbaines.net \
    /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.