* Re: [Emacs-diffs] master 14bb519: * lisp/emacs-lisp/package.el: New "external" package status
[not found] ` <E1YqNUr-0001A9-UH@vcs.savannah.gnu.org>
@ 2015-05-07 18:17 ` Stefan Monnier
2015-05-07 18:47 ` Artur Malabarba
0 siblings, 1 reply; 5+ messages in thread
From: Stefan Monnier @ 2015-05-07 18:17 UTC (permalink / raw
To: emacs-devel; +Cc: Artur Malabarba
> An external package is any installed package that's not built-in
> and not from `package-user-dir', which usually means it's from an
> entry in `package-directory-list'. They are treated much like
> built-in packages, in that they cannot be through the Package Menu
> deleted and are not considered for upgrades.
Good, thanks. I'd call them "system packages", tho. And we should
allow the user to install another version on top of it.
Stefan
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Emacs-diffs] master 14bb519: * lisp/emacs-lisp/package.el: New "external" package status
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-08 3:32 ` Stefan Monnier
0 siblings, 2 replies; 5+ messages in thread
From: Artur Malabarba @ 2015-05-07 18:47 UTC (permalink / raw
To: Stefan Monnier; +Cc: emacs-devel
2015-05-07 19:17 GMT+01:00 Stefan Monnier <monnier@iro.umontreal.ca>:
>> An external package is any installed package that's not built-in
>> and not from `package-user-dir', which usually means it's from an
>> entry in `package-directory-list'. They are treated much like
>> built-in packages, in that they cannot be through the Package Menu
>> deleted and are not considered for upgrades.
>
> Good, thanks. I'd call them "system packages", tho.
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
me to another topic.
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).
This way, if I want to manually download a package to a directory
that's NOT inside ~/.emacs.d/elpa, I can still have package.el
recognize its presence for the purpose of dependencies and such by
adding the directory to `package-directory-list'.
All the functionality already exists, I'm just wondering if I can
document that on the docstring or if there's a reason why this
variable is specifically meant for system packages.
> 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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Emacs-diffs] master 14bb519: * lisp/emacs-lisp/package.el: New "external" package status
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
1 sibling, 1 reply; 5+ messages in thread
From: Alan Mackenzie @ 2015-05-07 19:12 UTC (permalink / raw
To: Artur Malabarba; +Cc: Stefan Monnier, emacs-devel
Hello, Artur.
On Thu, May 07, 2015 at 07:47:29PM +0100, Artur Malabarba wrote:
> 2015-05-07 19:17 GMT+01:00 Stefan Monnier <monnier@iro.umontreal.ca>:
> >> An external package is any installed package that's not built-in
> >> and not from `package-user-dir', which usually means it's from an
> >> entry in `package-directory-list'. They are treated much like
> >> built-in packages, in that they cannot be through the Package Menu
> >> deleted and are not considered for upgrades.
The word order "they cannot be through the Package Menu deleted" is
wrong in English (it would be correct in German ;-). The correct word
order is "they cannot be deleted through the Package menu". I don't
think there's any reason to capitalise "menu" either, though I can see
"Package" might want to be capitalised.
Please consider amending your patch to the documentation.
--
Alan Mackenzie (Nuremberg, Germany).
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Emacs-diffs] master 14bb519: * lisp/emacs-lisp/package.el: New "external" package status
2015-05-07 19:12 ` Alan Mackenzie
@ 2015-05-07 19:30 ` Artur Malabarba
0 siblings, 0 replies; 5+ messages in thread
From: Artur Malabarba @ 2015-05-07 19:30 UTC (permalink / raw
To: Alan Mackenzie; +Cc: Stefan Monnier, emacs-devel
2015-05-07 20:12 GMT+01:00 Alan Mackenzie <acm@muc.de>:
> Hello, Artur.
>
> On Thu, May 07, 2015 at 07:47:29PM +0100, Artur Malabarba wrote:
>> 2015-05-07 19:17 GMT+01:00 Stefan Monnier <monnier@iro.umontreal.ca>:
>> >> An external package is any installed package that's not built-in
>> >> and not from `package-user-dir', which usually means it's from an
>> >> entry in `package-directory-list'. They are treated much like
>> >> built-in packages, in that they cannot be through the Package Menu
>> >> deleted and are not considered for upgrades.
>
> The word order "they cannot be through the Package Menu deleted" is
> wrong in English (it would be correct in German ;-). The correct word
> order is "they cannot be deleted through the Package menu". I don't
> think there's any reason to capitalise "menu" either, though I can see
> "Package" might want to be capitalised.
>
> Please consider amending your patch to the documentation.
Oops. I wish I could use German as an excuse, but it was really a typo. :-(
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Emacs-diffs] master 14bb519: * lisp/emacs-lisp/package.el: New "external" package status
2015-05-07 18:47 ` Artur Malabarba
2015-05-07 19:12 ` Alan Mackenzie
@ 2015-05-08 3:32 ` Stefan Monnier
1 sibling, 0 replies; 5+ messages in thread
From: Stefan Monnier @ 2015-05-08 3:32 UTC (permalink / raw
To: Artur Malabarba; +Cc: emacs-devel
> 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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2015-05-08 3:32 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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
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.