unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: Forcing reinstall in package.el
Date: Tue, 21 Dec 2010 08:42:19 -0700	[thread overview]
Message-ID: <m37hf35e04.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87oc8jdr4w.fsf@lifelogs.com> (Ted Zlatanov's message of "Sat, 18 Dec 2010 09:42:23 -0600")

Tom> I forgot to mention -- installing older versions can break dependencies.
Tom> The package activation code will handle this ok (it will not activate
Tom> such packages), but it will probably come as a surprise to the user when
Tom> some other package stops working.

Ted> Does this mean you're OK with the prompts otherwise?

Sure.

Ted> I think if the user asks to install an older version and forces
Ted> package.el to do it, they should be responsible for any breakage.

I just think it is friendlier to do the right thing instead of breaking
obscurely, and to make experts take an extra step instead of offering
non-expert users a choice that they are often ill-advised to take.

Ted> The prompt is too long already so I don't want to extend it with "...and
Ted> this will break installed packages if they depend on the newer
Ted> version."  But maybe package.el could show "broken" packages that can't
Ted> be activated because of the version mismatch?  Or is that already covered?

It doesn't show them specially right now, but I think it could.

Tom



      reply	other threads:[~2010-12-21 15:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 18:21 Forcing reinstall in package.el Phil Hagelberg
2010-12-14 21:28 ` Ted Zlatanov
2010-12-15  1:27   ` Phil Hagelberg
2010-12-15 14:55     ` Ted Zlatanov
2010-12-15 20:06       ` Tom Tromey
2010-12-15 21:54         ` Ted Zlatanov
2010-12-29 20:08           ` Phil Hagelberg
2011-01-19 20:18             ` Ted Zlatanov
2011-02-10 18:05             ` [PATCH] " Phil Hagelberg
2011-02-12  1:18               ` Chong Yidong
2010-12-17  4:10         ` Stefan Monnier
2010-12-17 14:17           ` Tom Tromey
2010-12-17 14:48             ` Ted Zlatanov
2010-12-17 15:56               ` Tom Tromey
2010-12-18 15:42                 ` Ted Zlatanov
2010-12-21 15:42                   ` Tom Tromey [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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m37hf35e04.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=emacs-devel@gnu.org \
    --cc=tzz@lifelogs.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).