all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: help-guix@gnu.org, John J Foerch <jjfoerch@earthlink.net>
Subject: Re: M-x guix bug
Date: Thu, 30 Jun 2016 23:21:10 +0200	[thread overview]
Message-ID: <87ziq2mkzd.fsf@gnu.org> (raw)
In-Reply-To: <87poqyagi0.fsf@gmail.com> (Alex Kost's message of "Thu, 30 Jun 2016 17:38:47 +0300")

Hello,

Alex Kost <alezost@gmail.com> skribis:

> I think the right thing would be to make "M-x guix" work by default.
> This can be done simply by adding 'magit-popup' dependency (i.e., by
> adding it to 'propagated-inputs') to our 'guix' package.  But if I
> understood correctly, Ludovic wouldn't like to do it:
> <http://lists.gnu.org/archive/html/guix-devel/2015-08/msg00576.html>

There are two separate issues here: one is the ‘guix’ package in Guix,
and another one is the required dependencies for those building from
source.

I’d rather have magit-popup be an optional dependency for someone
building from source.

I wouldn’t mind adding magit-popup as a dependency of the ‘guix’ package
in Guix if magit-popup were a separate package.  Currently, we’d need to
have ‘guix’ depend on ‘magit’, which is pretty big since it depends on
‘git’; not great.  Can magit-popup be made a separate package?

Thanks,
Ludo’.

  parent reply	other threads:[~2016-06-30 21:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 10:29 M-x guix bug John J Foerch
2016-06-28 21:58 ` Ludovic Courtès
2016-06-29  1:43   ` John J Foerch
2016-06-30 14:38     ` Alex Kost
2016-06-30 17:16       ` myglc2
2016-07-01  9:07         ` Alex Kost
2016-06-30 17:46       ` John J Foerch
2016-06-30 21:21       ` Ludovic Courtès [this message]
2016-07-01  2:48         ` myglc2
2016-07-01  9:02         ` Alex Kost
2016-07-01  9:30           ` Ludovic Courtès

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=87ziq2mkzd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=jjfoerch@earthlink.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.