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