| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Daniel Ostrow wrote: |
| 5 |
> On Wed, 2005-09-21 at 18:54 +0100, José Carlos Cruz Costa wrote: |
| 6 |
> |
| 7 |
>>Hi everybody, |
| 8 |
>> |
| 9 |
>>If it's commercial, the company in question should (and must) allow an |
| 10 |
>>ebuild for is product, like what happens with rpms and other packages. |
| 11 |
>>Adding commercial ebuilds to portage is like tainting the kernel with |
| 12 |
>>binary drivers. |
| 13 |
>> |
| 14 |
>>Maybe a better solution comes with gensync? If companies want ebuilds, |
| 15 |
>>sure. They go to the "commercial" portage. Hell, even put a price on |
| 16 |
>>maintaining those ebuilds. |
| 17 |
>> |
| 18 |
>>Remember that are a lot of people that don't want to use that kind of |
| 19 |
>>software. There are people that doesn't have even xorg and have to |
| 20 |
>>sync all the ebuilds from portage. |
| 21 |
> |
| 22 |
> This is what rsync excludes are for...there is no good reason to remove |
| 23 |
> things like doom3 and UT2k4 from the tree for the sole reason that they |
| 24 |
> are commercial packages. You don't want them...fine...exclude them. |
| 25 |
> |
| 26 |
|
| 27 |
Possible to make the default a non-commercial ebuild rsync ? The exclude |
| 28 |
file for rsync should be easy to make. That would be convenient for all |
| 29 |
and allow purist to keep their system clean. Also would allow coders to |
| 30 |
know what are the GNU weakest tools and work on them. |
| 31 |
|
| 32 |
It is a fact that I would like to be able to read what licenses I agree |
| 33 |
with and as a mater of fact I do not have to accept even GNU license to |
| 34 |
use gentoo, so in theory I would do it like this: |
| 35 |
|
| 36 |
|
| 37 |
After installing any stage any installation, the first action should |
| 38 |
generate something like: |
| 39 |
|
| 40 |
GPL/FSF license in the list of accepted licenses, please read |
| 41 |
/usr/portage/licenses/LICENSE and add the license to your make.conf file |
| 42 |
(only) if you accept it. |
| 43 |
|
| 44 |
Later on if I emerge some BSD licensed thing the same message should |
| 45 |
appear, commercial licenses too |
| 46 |
|
| 47 |
Otherwise the GLEP23 goes in the right direction. I know probably |
| 48 |
everyone hates the "reading" part of license agreement, but your own |
| 49 |
good read them at least once. And do not accept any commercial license |
| 50 |
without reading it properly, you can't guess what is implied in some cases. |
| 51 |
|
| 52 |
Phil |
| 53 |
-----BEGIN PGP SIGNATURE----- |
| 54 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 55 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
| 56 |
|
| 57 |
iD8DBQFDMmp5P0/FkJ0eBc0RAvLZAKC+Yof943+odO4x8ex5qVfL1WDJ1gCdF0gw |
| 58 |
cmOF+o5v2eI+kBglyGJFr1I= |
| 59 |
=9Msh |
| 60 |
-----END PGP SIGNATURE----- |
| 61 |
-- |
| 62 |
gentoo-dev@g.o mailing list |
Archives