Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #187103 > unrolled thread

Is there a list contains all debian packages and it's license ?

Back to article view | Back to linux.debian.user

Contents

  Is there a list contains all debian packages and it's license ? Yanhao Mo <yanhaocs@gmail.com> - 2017-09-23 02:50 +0200
    Re: Is there a list contains all debian packages and it's license  ? bw <bwtnguy@yahoo.com> - 2017-09-23 06:10 +0200
    Re: Is there a list contains all debian packages and it's license ? Paul Wise <pabs@debian.org> - 2017-09-23 08:40 +0200
      Re: Is there a list contains all debian packages and it's license ? Yanhao Mo <yanhaocs@gmail.com> - 2017-09-23 10:10 +0200
        Re: Is there a list contains all debian packages and it's license ? <tomas@tuxteam.de> - 2017-09-23 10:50 +0200
          Re: Is there a list contains all debian packages and it's license ? Simon McVittie <smcv@debian.org> - 2017-09-23 12:10 +0200
            Re: Is there a list contains all debian packages and it's license ? <tomas@tuxteam.de> - 2017-09-23 12:30 +0200

#187103 — Is there a list contains all debian packages and it's license ?

[Multipart message — attachments visible in raw view] — view raw

Hi,

I do known how to find license info about packages those have been
installed on my system and how to generate a list about it.
but what I really want to know is that is there such a list that display
all debian packages with their licenses, just like the following link
about rhel[1].

[1] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/Package_Manifest/index.html

Yanhao,

[toc] | [next] | [standalone]

#187107 — Re: Is there a list contains all debian packages and it's license ?

On Sat, 23 Sep 2017, Yanhao Mo wrote:

> but what I really want to know is that is there such a list that display
> all debian packages with their licenses, just like the following link


You use the phrase, "all debian packages" but what does that really mean?  

Debian provides links to packages that conform to it's own DFSG in a main 
repository.  There are various distributions, and ways to add packages to 
debian, so a list of "all debian packages with their licenses" might be 
difficult?

https://packages.debian.org/
https://www.debian.org/social_contract#guidelines
https://www.debian.org/legal/licenses/


.

[toc] | [prev] | [next] | [standalone]

#187113

On Sat, Sep 23, 2017 at 8:38 AM, Yanhao Mo wrote:

> but what I really want to know is that is there such a list that display
> all debian packages with their licenses, just like the following link
> about rhel[1].

There is no single list of licenses for each Debian package,
just the individual copyright files in each source/binary package.

What are you doing that requires a single list for all packages?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

[toc] | [prev] | [next] | [standalone]

#187115

[Multipart message — attachments visible in raw view] — view raw

On Sat, Sep 23, 2017 at 02:32:36PM +0800, Paul Wise wrote:
> On Sat, Sep 23, 2017 at 8:38 AM, Yanhao Mo wrote:
> 
> > but what I really want to know is that is there such a list that display
> > all debian packages with their licenses, just like the following link
> > about rhel[1].
> 
> There is no single list of licenses for each Debian package,
> just the individual copyright files in each source/binary package.
I see. Thanks for answering.
> What are you doing that requires a single list for all packages?
Nothing, I was just curious. :P

[toc] | [prev] | [next] | [standalone]

#187118

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Sep 23, 2017 at 04:05:49PM +0800, Yanhao Mo wrote:

[...]

> Nothing, I was just curious. :P

Not a readymade solution, but perhaps a lead to follow: package copyright
info is supposed to be in a file debian/copyright within the package source
archive[1]. I don't know at the moment whether this info percolates to
the package binary when building.

Note that one specific difficulty is that a package may consist of several
parts, all of them licensed differently.

There'san effort underway to make this license info machine readable [2]

Hope that helps to get you started

Cheers


[1] A debian source package is, basically, the original source hierarchy
   (aka "upstream") augmented by one subdirectory at top level, named
   "debian", containing debian specific patches, build recipes and all
   kind of debian specific metadata (dependency info, whatnot).
   This debian subdir is distributed as a separate .tar.gz
   cf. https://www.debian.org/doc/manuals/debian-handbook/sect.source-package-structure.en.html

[2] https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/

- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlnGGn0ACgkQBcgs9XrR2ka6bgCcCrKXjk2gy6thfCUJypOoLqnI
tecAnRNEuvdgDJ8uni9BU8l/pB5p5hgJ
=KIle
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#187123

On Sat, 23 Sep 2017 at 10:25:33 +0200, tomas@tuxteam.de wrote:
> Not a readymade solution, but perhaps a lead to follow: package copyright
> info is supposed to be in a file debian/copyright within the package source
> archive[1]. I don't know at the moment whether this info percolates to
> the package binary when building.

It does, and Debian Policy says it must. That information ends up in
/usr/share/doc/${binary_package}/copyright where ${binary_package} is the
binary package. For instance, the dbus source package produces binary
packages that include dbus, dbus-x11 and libdbus-1-3, so its
debian/copyright gets copied to /usr/share/doc/dbus/copyright,
/usr/share/doc/dbus-x11/copyright and /usr/share/doc/libdbus-1-3/copyright,
among others.

In rare cases the binary package copyright file is not identical to the
source copyright: if a package foo has a GPL part packaged as foo-utils
and a LGPL part packaged as libfoo0, it would be valid to list both GPL
and LGPL in debian/copyright, only GPL in /u/s/d/foo-utils/copyright
and only LGPL in /u/s/d/libfoo0/copyright. However, in practice
maintainers don't make use of this, because it creates extra work for
little or no benefit, and carries a risk of accidentally providing
incomplete or untrue copyright/licensing information.

    S

[toc] | [prev] | [next] | [standalone]

#187124

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Sep 23, 2017 at 11:08:34AM +0100, Simon McVittie wrote:
> On Sat, 23 Sep 2017 at 10:25:33 +0200, tomas@tuxteam.de wrote:
> > Not a readymade solution [...]

> It does, and Debian Policy says it must. That information ends up in
> /usr/share/doc/${binary_package}/copyright where ${binary_package} is the
> binary package [...]

Thanks, Simon: this fills a gap in my knowledge by providing the mising
piece :)

To the OP, since it seems to me that this wasn't explicit enough: a
Debian source packagee can be the origin of several binary packages.
A typical case wold be an SQL server, whose source contains server,
server libs, client and client libs -- but you don't want to install
the whole kaboodle in your embedded box which just wants to access
a database.

Cheers
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlnGNngACgkQBcgs9XrR2kaGCQCdHWfn0O844cuNYR61+nOkL+Pm
DT0An0qFbZgF1k0+qQNLo2UhJqo4G+1j
=53OW
-----END PGP SIGNATURE-----

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web