1 |
On Sun, Jan 22, 2006 at 02:59:39PM -0700, Joshua Baergen wrote: |
2 |
> Joshua Baergen wrote: |
3 |
> >The reasons that this system was chosen were correctness and |
4 |
> >maintainability. Many of these essentially use the good old MIT |
5 |
> >license with various companies' and/or individuals' copyrights at the |
6 |
> >top, as you have stated. However, the MIT license does refer to the |
7 |
> >copyrights within the license script itself, and many of the licenses |
8 |
> >have been slightly altered to include a company's name directly. I'm |
9 |
> >no lawyer, but to me this means that the license does indeed include |
10 |
> >the copyright. (Note that I'm not intricately familiar with other |
11 |
> >licenses that often have copyrights associated, so I don't know if MIT |
12 |
> >is unique). If this isn't correct, I'd be very happy to switch all |
13 |
> >the packages that use various forms of the MIT license over to it |
14 |
> >instead and you can blissfully ignore the next paragraph. However, |
15 |
> >I'd rather be on the safe/correct side than save a few MB that have to |
16 |
> >be downloaded once. |
17 |
> > |
18 |
> ><snip> |
19 |
> > |
20 |
> >Joshua Baergen |
21 |
> I'd still like clarification on this. I fully realize that we've been |
22 |
> using generalized placeholders for a long time, but that doesn't really |
23 |
> matter in the end if it's not legal. |
24 |
|
25 |
What leads you to believe the license texts distributed in portage tree |
26 |
are legaly binding with respect to the packages? Each packgage carries |
27 |
(or at least should carry) its license embeded inside. In my |
28 |
understanding, licanse pointers in ebuilds are purely informative and |
29 |
allow you to check the terms of the license (and decide if the license |
30 |
is acceptable) before you actually perform any legaly binding action |
31 |
(like running 'emerge app-foo/bar'). |
32 |
|
33 |
Regards, |
34 |
Peter Cech |
35 |
-- |
36 |
gentoo-dev@g.o mailing list |