From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Sebastian Wiesner <lunaryorn@gmail.com>
Cc: Steve Purcell <steve@sanityinc.com>,
Donald Curtis <dcurtis@milkbox.net>,
emacs-devel@gnu.org
Subject: Re: MELPA version numbers
Date: Fri, 02 Aug 2013 11:47:59 -0400 [thread overview]
Message-ID: <jwvehacayml.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CALf2awRpDygkitOdU419wG6zHdfJ2+kJitVGQ5_Ceq9oYr2-7A@mail.gmail.com> (Sebastian Wiesner's message of "Fri, 2 Aug 2013 17:24:16 +0200")
> Indeed, I just discovered "package-pinned-packages", which I presume
> is what you are referring to. In theory it's a nice feature, but I
> really dislike the current implementation. I am actually a bit
> disappointed about the quick hack that was use to implement this
> feature: When reading the package archives, package.el appears to just
> ignore(!) all package versions which are pinned to another archive.
Right, I haven't upgraded the code to follow the new style (filter
late, rather than filter early) for package-pinned-packages.
Patch welcome.
> and API of package.el. I manage my packages through Carton (, and
> Carton has to
Ah, well if Carton has to
>> 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.
> Or, in other words, if a GNU ELPA package happens to be more recent
> than MELPA, that's a failure in MELPA,
That's right.
Stefan
next prev parent reply other threads:[~2013-08-02 15:47 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 [this message]
2013-08-02 15:58 ` Steve Purcell
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=jwvehacayml.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dcurtis@milkbox.net \
--cc=emacs-devel@gnu.org \
--cc=lunaryorn@gmail.com \
--cc=steve@sanityinc.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.