Gentoo Archives: gentoo-dev

From: "Michał Górny" <mgorny@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Last rites: games-rpg/nwn-shadowlordsdreamcatcherdemon
Date: Thu, 07 Sep 2017 21:18:22
Message-Id: 1504819091.32100.3.camel@gentoo.org
In Reply to: Re: [gentoo-dev] Last rites: games-rpg/nwn-shadowlordsdreamcatcherdemon by Rich Freeman
1 W dniu czw, 07.09.2017 o godzinie 16∶42 -0400, użytkownik Rich Freeman
2 napisał:
3 > On Thu, Sep 7, 2017 at 4:36 PM, Michał Górny <mgorny@g.o> wrote:
4 > > W dniu czw, 07.09.2017 o godzinie 06∶21 -0700, użytkownik Rich Freeman
5 > > napisał:
6 > > > On Thu, Sep 7, 2017 at 6:04 AM, Ulrich Mueller <ulm@g.o> wrote:
7 > > > > > > > > > On Thu, 7 Sep 2017, Rich Freeman wrote:
8 > > > >
9 > > > > Don't you think there is a difference between downloading a package
10 > > > > that has a known upstream and that is also carried by other distros,
11 > > > > and downloading a license-less package from a random location on the
12 > > > > internet?
13 > > >
14 > > > Most upstreams do not do much checking about the ownership of their sources.
15 > > >
16 > > > Gentoo certainly doesn't - we don't even require developers to submit a DCO.
17 > > >
18 > > > Other projects like the Linux kernel require signing a DCO for each
19 > > > commit, but do not do any checking beyond this. I have no doubt that
20 > > > they would remove offending sources if they were contacted, but they
21 > > > do not actively go out and confirm authorship.
22 > > >
23 > > > >
24 > > > > > > The package in question doesn't come with any license though, which
25 > > > > > > means that only the copyright holder has the right to distribute
26 > > > > > > it. So I believe that some extra care is justified, especially when
27 > > > > > > the upstream location of the distfile has changed.
28 > > > > >
29 > > > > > Why? We don't redistribute anything that is copyrighted.
30 > > > >
31 > > > > Users download the file, and I think that we are responsible to have
32 > > > > only such SRC_URIs in our ebuilds from where they can obtain the
33 > > > > package without being exposed to potential legal issues.
34 > > >
35 > > > I'm not aware of any court rulings that have found downloading
36 > > > something like this to be illegal.
37 > > >
38 > > > >
39 > > > > > Perhaps if we want to enforce a policy like this we should take the
40 > > > > > time to actually write the policy down. As far as I can tell Gentoo
41 > > > > > has no such policy currently.
42 > > > >
43 > > > > The old Games Ebuild Howto [1] has this:
44 > > > >
45 > > > > > LICENSE
46 > > > > >
47 > > > > > The license is an important point in your ebuild. It is also a
48 > > > > > common place for making mistakes. Try to check the license on any
49 > > > > > ebuild that you submit. Often times, the license will be in a
50 > > > > > COPYING file, distributed in the package's tarball. If the license
51 > > > > > is not readily apparent, try contacting the authors of the package
52 > > > > > for clarification. [...]
53 > > > >
54 > > > > I propose to add the paragraph above to the devmanual's licenses
55 > > > > section.
56 > > > >
57 > > >
58 > > > We already know there isn't a license for redistribution. This
59 > > > doesn't speak about requiring us to ensure that those distributing our
60 > > > source files have the rights to do so. It merely says to check the
61 > > > license. We understand the license already. I don't see how this
62 > > > paragraph pertains to this situation.
63 > >
64 > > AFAIK you're a developer. So if you want to keep this package, then
65 > > please do the needful and take care of it yourself instead of
66 > > complaining and demanding others to do the work you want done.
67 > >
68 >
69 > Are you saying it is sufficient to just point the SRC_URI at the new
70 > URL and remove the mask? As far as I can tell that is all that needs
71 > to be done. Per the policy the license is readily apparent, so there
72 > is no need to contact the authors.
73 >
74
75 I don't know what is sufficient. It's your business as the new
76 maintainer to figure it out and take the responsibility. If there's
77 nobody willing to do that, then we don't get to keep the package. Simple
78 as that.
79
80 --
81 Best regards,
82 Michał Górny

Replies