* bug#16250: Feature request: package license information and home page
@ 2013-12-25 5:09 Dave Abrahams
2013-12-25 16:56 ` Stefan Monnier
2019-07-14 16:12 ` Stefan Kangas
0 siblings, 2 replies; 7+ messages in thread
From: Dave Abrahams @ 2013-12-25 5:09 UTC (permalink / raw)
To: 16250
[-- Attachment #1: Type: text/plain, Size: 266 bytes --]
There should be an easy way to find out the
license information and other metadata about a package before installing
it. Ideally this information should show up in the results of
package-menu-describe-package
Thanks for entertaining my request,
--
Dave Abrahams
[-- Attachment #2: Type: text/html, Size: 404 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#16250: Feature request: package license information and home page
2013-12-25 5:09 bug#16250: Feature request: package license information and home page Dave Abrahams
@ 2013-12-25 16:56 ` Stefan Monnier
2013-12-26 5:59 ` Dave Abrahams
2019-07-14 16:12 ` Stefan Kangas
1 sibling, 1 reply; 7+ messages in thread
From: Stefan Monnier @ 2013-12-25 16:56 UTC (permalink / raw)
To: Dave Abrahams; +Cc: 16250
> There should be an easy way to find out the license information and
Why?
> other metadata about a package before installing it.
Which other metadata?
Stefan
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#16250: Feature request: package license information and home page
2013-12-25 16:56 ` Stefan Monnier
@ 2013-12-26 5:59 ` Dave Abrahams
2013-12-26 12:46 ` Stefan Monnier
0 siblings, 1 reply; 7+ messages in thread
From: Dave Abrahams @ 2013-12-26 5:59 UTC (permalink / raw)
To: Stefan Monnier; +Cc: 16250@debbugs.gnu.org
Sent from my moss-covered three-handled family gradunza
On Dec 25, 2013, at 8:56 AM, Stefan Monnier <monnier@IRO.UMontreal.CA> wrote:
>> There should be an easy way to find out the license information and
>
> Why?
Some people (like me) are picky about the license terms of software that they download, especially in source form.
>> other metadata about a package before installing it.
>
> Which other metadata?
For example, a package's home page, author, maybe date of last update, etc.
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#16250: Feature request: package license information and home page
2013-12-26 5:59 ` Dave Abrahams
@ 2013-12-26 12:46 ` Stefan Monnier
2013-12-27 18:23 ` Dave Abrahams
0 siblings, 1 reply; 7+ messages in thread
From: Stefan Monnier @ 2013-12-26 12:46 UTC (permalink / raw)
To: Dave Abrahams; +Cc: 16250@debbugs.gnu.org
>>> There should be an easy way to find out the license information and
>> Why?
> Some people (like me) are picky about the license terms of software that
> they download, especially in source form.
Give me some examples of Elisp packages where that would be useful.
>>> other metadata about a package before installing it.
>> Which other metadata?
> For example, a package's home page, author, maybe date of last update, etc.
The home page is already available, AFAIK. Author/maintainer could
be provided. Date of last update is generally not kept (tho in
elpa.gnu.org/packages you can indeed see it, tho it's really the date
at which the tarball was created).
I think the better option is to let the user separate the "download" and
"install" steps so she can look at those extra info before installing.
Stefan
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#16250: Feature request: package license information and home page
2013-12-26 12:46 ` Stefan Monnier
@ 2013-12-27 18:23 ` Dave Abrahams
2013-12-27 21:44 ` Stefan Monnier
0 siblings, 1 reply; 7+ messages in thread
From: Dave Abrahams @ 2013-12-27 18:23 UTC (permalink / raw)
To: Stefan Monnier; +Cc: 16250@debbugs.gnu.org
[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]
On Thu, Dec 26, 2013 at 4:46 AM, Stefan Monnier <monnier@iro.umontreal.ca>wrote:
> >>> There should be an easy way to find out the license information and
> >> Why?
> > Some people (like me) are picky about the license terms of software that
> > they download, especially in source form.
>
> Give me some examples of Elisp packages where that would be useful.
>
Any package is a potential example. I’m not sure what you’re looking for
here, and I don’t suppose you want an arbitrary list of the first 50
packages listed at MELPA. If you could explain what you’re after maybe I
could say something useful.
> >>> other metadata about a package before installing it.
> >> Which other metadata?
> > For example, a package's home page, author, maybe date of last update,
> etc.
>
> The home page is already available, AFAIK. Author/maintainer could
> be provided. Date of last update is generally not kept (tho in
> elpa.gnu.org/packages you can indeed see it, tho it's really the date
> at which the tarball was created).
>
> I think the better option is to let the user separate the "download" and
> "install" steps so she can look at those extra info before installing.
That won’t help people whose employers have specific rules restricting the
license terms of code that may be *downloaded to the employers’ machines*
without prior approval.
--
Dave Abrahams
[-- Attachment #2: Type: text/html, Size: 2109 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#16250: Feature request: package license information and home page
2013-12-27 18:23 ` Dave Abrahams
@ 2013-12-27 21:44 ` Stefan Monnier
0 siblings, 0 replies; 7+ messages in thread
From: Stefan Monnier @ 2013-12-27 21:44 UTC (permalink / raw)
To: Dave Abrahams; +Cc: 16250@debbugs.gnu.org
>> > Some people (like me) are picky about the license terms of software that
>> > they download, especially in source form.
>> Give me some examples of Elisp packages where that would be useful.
> Any package is a potential example.
99.9% of Elisp packages are licensed under the GPL. I doubt these would
be convincing examples of the need to check the licensing info.
And the remaining 0.1% is licensed under a GPL-compatible license, BTW
(because any Elisp package necessarily links to GPL'd code, either
Emacs's or XEmacs's, so it's basically illegal to distribute Elisp code
under anything else than a GPL-compatible license).
> If you could explain what you’re after maybe I could say
> something useful.
An example package where it can be useful to know what license is used.
Stefan
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#16250: Feature request: package license information and home page
2013-12-25 5:09 bug#16250: Feature request: package license information and home page Dave Abrahams
2013-12-25 16:56 ` Stefan Monnier
@ 2019-07-14 16:12 ` Stefan Kangas
1 sibling, 0 replies; 7+ messages in thread
From: Stefan Kangas @ 2019-07-14 16:12 UTC (permalink / raw)
To: Stefan Monnier; +Cc: Dave Abrahams, 16250@debbugs.gnu.org
tags 16250 + wontfix
close 16250
thanks
Dave Abrahams <dave@boostpro.com> writes:
> There should be an easy way to find out the
> license information and other metadata about a package before installing
> it. Ideally this information should show up in the results of
> package-menu-describe-package
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>>> > Some people (like me) are picky about the license terms of software that
>>> > they download, especially in source form.
>>> Give me some examples of Elisp packages where that would be useful.
>> Any package is a potential example.
>
> 99.9% of Elisp packages are licensed under the GPL. I doubt these would
> be convincing examples of the need to check the licensing info.
> And the remaining 0.1% is licensed under a GPL-compatible license, BTW
> (because any Elisp package necessarily links to GPL'd code, either
> Emacs's or XEmacs's, so it's basically illegal to distribute Elisp code
> under anything else than a GPL-compatible license).
>
>> If you could explain what you’re after maybe I could say
>> something useful.
>
> An example package where it can be useful to know what license is used.
That was in 2013, and I agree with Stefan that this feature doesn't sound worth
it. It's all GPL compatible. FWIW, Debian doesn't show this in aptitude
either.
The homepage is already available in package-menu-describe-package.
I've therefore closed this as wontfix. If anyone disagrees, feel free
to re-open.
Best regards,
Stefan Kangas
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2019-07-14 16:12 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-25 5:09 bug#16250: Feature request: package license information and home page Dave Abrahams
2013-12-25 16:56 ` Stefan Monnier
2013-12-26 5:59 ` Dave Abrahams
2013-12-26 12:46 ` Stefan Monnier
2013-12-27 18:23 ` Dave Abrahams
2013-12-27 21:44 ` Stefan Monnier
2019-07-14 16:12 ` Stefan Kangas
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.