1 |
Hi |
2 |
|
3 |
> It's not simple. You have to learn the requirements of each license |
4 |
> and see if and how they allow themselves to be combined. There are |
5 |
> businesses doing exactly that. If you want to DIY I think you just |
6 |
> have to start by reading the licenses. You may or may not want an |
7 |
> IP lawyer sitting beside you while doing it. |
8 |
|
9 |
This is the kind of unhelpful answer that I can find plenty of examples |
10 |
of through google... |
11 |
|
12 |
Consider that all software comes with some kind of licence. Generally |
13 |
if you ask a non opensource company about licensing costs then even the |
14 |
sales droid can help you out. I do find it quite baffling that on |
15 |
average if you question an opensource user then their answer on |
16 |
licensing is that one should redirect the question to one of the most |
17 |
expensive and opaque professions on earth... If your mate gave you that |
18 |
answer in the pub when you asked what price for a beer you would |
19 |
immediately cotton on that they don't really know and are bluffing... |
20 |
|
21 |
The bit people seem to miss is that legal documents are for forcing |
22 |
arbitration in the event of dispute - in the meantime people are |
23 |
supposed to rub along in a cooperative manner. That many OSS advocates |
24 |
seem to feel that employing expensive lawyers is the only way to talk to |
25 |
them shows that they are probably missing the bigger picture... |
26 |
|
27 |
On a more constructive note: I think I do understand the key terms of |
28 |
the main software licences we use, from my understanding they are not |
29 |
all that onerous. So can we perhaps move this topic onto tips, |
30 |
suggestions and practical matters about moving forward? I'm not sure |
31 |
that one of the most expensive type of lawyers is best employed talking |
32 |
scripting tips? |
33 |
|
34 |
> If you have patches which use a different license than the package |
35 |
> they modify then you have more work to do. Portage doesn't help here. |
36 |
> A good start would be to add record of all patches applied by emerge. |
37 |
> Indeed add it into the epatch command. |
38 |
|
39 |
OK, so this is what I asked the list. Please don't turn it back at me... |
40 |
|
41 |
Firstly can we not assume that the patches in gentoo *are* in |
42 |
compliance, otherwise gentoo's various packaged binaries would cause |
43 |
Gentoo to be out of compliance? (I'm going to assume that human error |
44 |
will cause at least some mistakes, but lets hope that just like Gentoo |
45 |
isn't being sued right now, copyright holders are actually going to be |
46 |
cooperative in fixing minor issues...!) |
47 |
|
48 |
|
49 |
So, back to the problem: one of the bigger challenges seems to be how to |
50 |
actually capture the absolute list of patches applied? Any |
51 |
suggestions? I already suggested creating my own "patch" utility which |
52 |
saves it's input - seems ugly - other suggestions? |
53 |
|
54 |
I'm not using catalyst. Any tips from others on capturing, presenting, |
55 |
managing and deploying GPL code? |
56 |
|
57 |
Hoping for useful answers here rather than "talk to some really |
58 |
expensive professional who knows nothing about programming". |
59 |
|
60 |
Gentoo seems very attractive for building embedded system - however, |
61 |
there seem to be some missing steps to help with deployment. I thought |
62 |
that was ontopic for this list? Any tips from others who are building |
63 |
things? |
64 |
|
65 |
|
66 |
Cheers |
67 |
|
68 |
Ed W |