all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: chad <yandros@gmail.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] scratch/package-fix e5d5cdf 1/2: emacs-lisp/package.el: Indicate incompatible packages.
Date: Fri, 13 Feb 2015 20:18:10 +0000	[thread overview]
Message-ID: <CAAdUY-KiEpnw1rRypmbeE7oa9_bhvkZfrWcKZb4X5QQSs8O8+Q@mail.gmail.com> (raw)
In-Reply-To: <jwvwq3l4lmr.fsf-monnier+emacsdiffs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 461 bytes --]

> Maybe you're right.  Just like installation may fail because
> a dependency is missing.  Maybe marking those things as
> uninstallable/incompatible is good, but only if we can explain
> concisely/easily enough to the user why it's uninstallable/incompatible.

Yes, it would be good to add that to the describe package buffer.
package--incompatible-p already returns the reason why the package is
incompatible, so it's just a matter of formating and printing.

[-- Attachment #2: Type: text/html, Size: 538 bytes --]

  reply	other threads:[~2015-02-13 20:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150211170820.10979.16862@vcs.savannah.gnu.org>
     [not found] ` <E1YLalx-0002s8-E8@vcs.savannah.gnu.org>
2015-02-11 19:28   ` [Emacs-diffs] scratch/package-fix e5d5cdf 1/2: emacs-lisp/package.el: Indicate incompatible packages Stefan Monnier
2015-02-11 23:00     ` Artur Malabarba
2015-02-12 14:41       ` Stefan Monnier
2015-02-12 16:35         ` Davis Herring
2015-02-13 13:48           ` Artur Malabarba
2015-02-12 21:42         ` chad
2015-02-13 20:13           ` Stefan Monnier
2015-02-13 20:18             ` Artur Malabarba [this message]
2015-02-14 18:04               ` Artur Malabarba

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=CAAdUY-KiEpnw1rRypmbeE7oa9_bhvkZfrWcKZb4X5QQSs8O8+Q@mail.gmail.com \
    --to=bruce.connor.am@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=yandros@gmail.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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.