From: Jorgen Schaefer <forcer@forcix.cx>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 19296@debbugs.gnu.org
Subject: bug#19296: [PATCH] Package archives now have priorities.
Date: Mon, 15 Dec 2014 09:36:10 +0100 [thread overview]
Message-ID: <548E9D7A.5090802@forcix.cx> (raw)
In-Reply-To: <jwvppblecs2.fsf-monnier+emacsbugs@gnu.org>
On 12/15/2014 05:59 AM, Stefan Monnier wrote:
>> What requirements would a patch need to fulfill that you deem it
>> acceptable to be applied to the Emacs repository that solves my
>> original problem (i.e. only install packages from a given repository if
>> the package is not available from other repositories)?
>
> I'd like a solution that also addresses, at least partly, the other
> problem (the one where the MELPA version is superseded by a version
> elsewhere such as in GNU ELPA).
>
> It's not important to automatically upgrade the package from the MELPA
> version to the GNU ELPA version, but the user should somehow be warned
> at some point that the MELPA version is not the latest any more.
So a warning "this package was installed from archive X, but is not
available from there anymore" would suffice to fulfill this requirement,
correct? Would it be enough if the package list displayed a string like
"changed archive" or similar? (This needs a shorter name.)
> I think in general it would be desirable to try and remember where
> a package came from so that upgrading to a version in another repository
> doesn't happen automatically.
I can see two ways for this. One, we overwrite the package's -pkg.el
file on install time with an expanded version that includes our own
infos, e.g. :archive "name" for this
(`package-generate-description-file' already has the code to generate
this file, and it just needs to be called even if the file already
exists). Alternatively, we add an .archive file to the package directory
recording the archive this came from.
I would tend to lean to overriding the -pkg.el file, but I do not have
any big preferences. Which way would you prefer?
In either case, we should populate the pkg-desc in `package-alist' from
this, which should make it easy to implement the display above.
If I add this functionality, will that make the reminder of the patch
acceptable to be included in Emacs?
Regards,
Jorgen
next prev parent reply other threads:[~2014-12-15 8:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 12:31 bug#19296: [PATCH] Package archives now have priorities Jorgen Schaefer
2014-12-07 16:07 ` Ted Zlatanov
2014-12-07 17:56 ` Stefan Monnier
2014-12-07 18:21 ` Jorgen Schaefer
2014-12-07 20:00 ` Jorgen Schaefer
2014-12-08 2:48 ` Stefan Monnier
2014-12-08 10:58 ` Jorgen Schaefer
2014-12-08 15:42 ` Stefan Monnier
2014-12-08 18:49 ` Jorgen Schaefer
2014-12-15 4:59 ` Stefan Monnier
2014-12-15 8:36 ` Jorgen Schaefer [this message]
2014-12-15 12:08 ` Ted Zlatanov
2014-12-15 14:52 ` Stefan Monnier
2014-12-15 14:55 ` Jorgen Schaefer
2014-12-15 19:07 ` Stefan Monnier
2014-12-07 18:55 ` Achim Gratz
2014-12-08 2:45 ` Stefan Monnier
2014-12-08 7:22 ` Achim Gratz
2014-12-07 21:28 ` Jorgen Schaefer
2014-12-07 21:46 ` Jorgen Schaefer
[not found] <<20141207132244.A14A7200D1E@loki.jorgenschaefer.de>
2014-12-07 14:19 ` Drew Adams
2014-12-07 14:43 ` Jorgen Schaefer
2014-12-07 15:55 ` Drew Adams
2014-12-07 16:10 ` Jorgen Schaefer
2014-12-07 18:16 ` Drew Adams
2014-12-07 16:13 ` Ted Zlatanov
2014-12-07 17:41 ` Stefan Monnier
[not found] ` <<20141207214345.A8216200D2E@loki.jorgenschaefer.de>
2014-12-07 22:27 ` Drew Adams
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=548E9D7A.5090802@forcix.cx \
--to=forcer@forcix.cx \
--cc=19296@debbugs.gnu.org \
--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.