1 |
* Ed W <lists@××××××××××.com> [120303 13:29]: |
2 |
> Hi |
3 |
> |
4 |
[..] |
5 |
|
6 |
> >> My understanding is that for a GPL licence one should provide a |
7 |
> >> copy of these patches in the "code dump", not just an http link? |
8 |
> >> Is that your understanding? |
9 |
> > I think your understanding is incomplete, and I recommend that you |
10 |
> > read through the license again. |
11 |
> |
12 |
> ?? Why all the stupid hints rather than just stating the answer! |
13 |
|
14 |
I'm sure it's just frustration but your emails really make you sound |
15 |
like an a-hole with a sense of entitlement. |
16 |
|
17 |
They're legal licenses. As with anything involved with lawyers and the |
18 |
legal system you really need to decide for yourself what needs to be |
19 |
done (most people to be safe would contact a lawyer.) |
20 |
|
21 |
If you're at a company releasing a product then the company most likely |
22 |
has a legal dept or legal consultant. They certainly would here in the |
23 |
US (I know you said you're not in the US so perhaps that's not the |
24 |
case.) |
25 |
|
26 |
Have you looked at http://www.gnu.org/licenses/gpl-faq.html? |
27 |
|
28 |
I'm not a lawyer (by a far shot) but what's the problem with creating a |
29 |
script that when run pulls the upstream files from |
30 |
/usr/portage/distfiles, the files and ebuilds from /usr/portage for |
31 |
whatever packages you have installed on whatever you're releasing? |
32 |
|
33 |
If I were releasing commercial software I'd want all that on a local |
34 |
mirror (in source control too) so that I could recreate any released |
35 |
versions. |
36 |
|
37 |
Todd |