From: Steve Purcell <steve@sanityinc.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Sebastian Wiesner <lunaryorn@gmail.com>,
Donald Curtis <dcurtis@milkbox.net>,
emacs-devel@gnu.org
Subject: Re: MELPA version numbers
Date: Fri, 2 Aug 2013 16:58:34 +0100 [thread overview]
Message-ID: <09A65E9C-9B66-4925-AA4C-F07523248CCD@sanityinc.com> (raw)
In-Reply-To: <jwvehacayml.fsf-monnier+emacs@gnu.org>
On 2 Aug 2013, at 16:47, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>>> No, it doesn't really solve the problem: most people wouldn't know when
>>> MELPA's version is out of date. How would you know to switch archive if
>>> package.el doesn't tell you that there's a newer version in the
>>> "gnu" archive?
>> How exactly can that happen given that MELPA *always* builds VCS
>> snapshots, with are *by definition* the most recent state of a
>> package?
>
> Steve asks similarly:
>> Can that even happen, for longer than a MELPA build cycle?
>
> Well, it can happen (and has happened, IIRC I saw it for csv-mode, tho
> it seems to be fixed now) because MELPA gives you the latest revision of
> the DVCS branch it point at, but that branch may be abandoned.
Yes, that would be a fault in MELPA's recipe; we've typically corrected this promptly when it has arisen previously, but I agree that there's no easy way to detect this situation.
-Steve
next prev parent reply other threads:[~2013-08-02 15:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 17:50 MELPA version numbers Stefan Monnier
2013-08-01 20:49 ` Donald Curtis
2013-08-01 21:39 ` Stefan Monnier
2013-08-02 8:26 ` Sebastian Wiesner
2013-08-02 14:27 ` Stefan Monnier
2013-08-02 14:35 ` Steve Purcell
2013-08-02 15:24 ` Sebastian Wiesner
2013-08-02 15:47 ` Stefan Monnier
2013-08-02 15:58 ` Steve Purcell [this message]
2013-08-01 20:51 ` Sebastian Wiesner
2013-08-01 20:57 ` Dmitry Gutov
2013-08-02 14:46 ` Steve Purcell
2013-08-02 15:57 ` Stefan Monnier
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=09A65E9C-9B66-4925-AA4C-F07523248CCD@sanityinc.com \
--to=steve@sanityinc.com \
--cc=dcurtis@milkbox.net \
--cc=emacs-devel@gnu.org \
--cc=lunaryorn@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.