From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] master 14bb519: * lisp/emacs-lisp/package.el: New "external" package status
Date: Thu, 07 May 2015 23:32:26 -0400 [thread overview]
Message-ID: <jwvy4kzlpcn.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <CAAdUY-LAunypMHioXvK-Ua0xCqyuoah4T3dVQj4xuuyYHRrrsw@mail.gmail.com> (Artur Malabarba's message of "Thu, 7 May 2015 19:47:29 +0100")
> I didn't call them "system" because they might just have been
> installed by the user. I can change that if preferred, but that brings
I don't have a strong opinion on that.
> The docstring of `package-directory-list' says it is intended for
> system-wide packages. But it seems to me that it would work perfectly
> fine for the user's manually installed packages (in fact, that's what
> I'm doing here).
I put the elpa/packages directory in there too (and elpa/README
suggests doing so as well).
But I tend to think of this case as "installed by my sysadmin-half".
>> And we should allow the user to install another version on top of it.
> I think we already do. If a more recent version is available from the
> archives it is still shown in the menu. It just won't be automatically
> marked for installation with the `U' key.
Are, perfect then, thanks,
Stefan
prev parent reply other threads:[~2015-05-08 3:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150507151357.4431.95466@vcs.savannah.gnu.org>
[not found] ` <E1YqNUr-0001A9-UH@vcs.savannah.gnu.org>
2015-05-07 18:17 ` [Emacs-diffs] master 14bb519: * lisp/emacs-lisp/package.el: New "external" package status Stefan Monnier
2015-05-07 18:47 ` Artur Malabarba
2015-05-07 19:12 ` Alan Mackenzie
2015-05-07 19:30 ` Artur Malabarba
2015-05-08 3:32 ` Stefan Monnier [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvy4kzlpcn.fsf-monnier+emacsdiffs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=bruce.connor.am@gmail.com \
--cc=emacs-devel@gnu.org \
/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.