Ian Stakenvicius schrieb:
> IE: - -'as-is' would be the generic "as-is" statement -
> -'free-non-commercial' would be a "free/unrestricted for 
> non-commercial use" statement - -'free-unrestricted' would be a
> statement of more or less public domain
> 
> - -..etc...

Why not directly use the FSF freedoms:
The freedom to run the program, for any purpose (freedom 0).
The freedom to study how the program works, and change it so it does
your computing as you wish (freedom 1).
The freedom to redistribute copies so you can help your neighbor
(freedom 2).
The freedom to distribute copies of your modified versions to others
(freedom 3).

I think when combined appropriately, they nicely cover most of the
cases of current "as-is" packages.

> ..and then ebuilds can include the particular phrases that apply?
> ie, LICENSE="(as-is free-non-commercial)" , essentially an 
> 'assemble-your-own-license' from the snippets.

We would maybe have to find a different operator for license
concatenation.


Best regards,
Chí-Thanh Christopher Nguyễn


Reply via email to