[6/8] fontconfig: add license info

Signed-off-by: Danomi Manchego <danomimanchego123@gmail.com>
---
 package/fontconfig/fontconfig.mk |    2 ++
 1 file changed, 2 insertions(+)

Le Sun, 19 Aug 2012 16:18:28 -0400,
Danomi Manchego <danomimanchego123@gmail.com> a écrit :

> +FONTCONFIG_LICENSE = fontconfig
> +FONTCONFIG_LICENSE_FILES = COPYING

For special licenses, I thought that the convention was to use the
string "foo license", and not just "foo". Luca?

Thomas

> For special licenses, I thought that the convention was to use the
> string "foo license", and not just "foo".

Grepping, I see only three exceptions to this:

package/zxing/zxing.mk:ZXING_LICENSE = Apache
package/poco/poco.mk:POCO_LICENSE = Boost-v1.0
package/openssl/openssl.mk:OPENSSL_LICENSE = OpenSSL or SSLeay

So, I'll resubmit as "fontconfig license".

What about sqlite?  According to http://www.sqlite.org/copyright.html, it
is "public domain".  Should sqlite's license also be "sqlite license", or
"public domain"?

Danomi -


On Tue, Aug 21, 2012 at 6:56 AM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Le Sun, 19 Aug 2012 16:18:28 -0400,
> Danomi Manchego <danomimanchego123@gmail.com> a écrit :
>
> > +FONTCONFIG_LICENSE = fontconfig
> > +FONTCONFIG_LICENSE_FILES = COPYING
>
> For special licenses, I thought that the convention was to use the
> string "foo license", and not just "foo". Luca?
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
>

Hi Danomi,

On Tue, Aug 21, 2012 at 08:39:26PM -0400, Danomi Manchego wrote:
> > For special licenses, I thought that the convention was to use the
> > string "foo license", and not just "foo".
> 
> Grepping, I see only three exceptions to this:
> 
> package/zxing/zxing.mk:ZXING_LICENSE = Apache
> package/poco/poco.mk:POCO_LICENSE = Boost-v1.0

Apache and Boost refer (also) to specific software licenses. See 
http://www.apache.org/licenses/ and http://www.boost.org/users/license.html. I 
think we should add a version number to Apache license info, though. In the 
case of zxing it's v2.0.

baruch

> package/openssl/openssl.mk:OPENSSL_LICENSE = OpenSSL or SSLeay
> 
> So, I'll resubmit as "fontconfig license".
> 
> What about sqlite?  According to http://www.sqlite.org/copyright.html, it
> is "public domain".  Should sqlite's license also be "sqlite license", or
> "public domain"?
> 
> Danomi -
> On Tue, Aug 21, 2012 at 6:56 AM, Thomas Petazzoni <
> thomas.petazzoni@free-electrons.com> wrote:
> 
> > Le Sun, 19 Aug 2012 16:18:28 -0400,
> > Danomi Manchego <danomimanchego123@gmail.com> a écrit :
> >
> > > +FONTCONFIG_LICENSE = fontconfig
> > > +FONTCONFIG_LICENSE_FILES = COPYING
> >
> > For special licenses, I thought that the convention was to use the
> > string "foo license", and not just "foo". Luca?
> >
> > Thomas
> > --
> > Thomas Petazzoni, Free Electrons
> > Kernel, drivers, real-time and embedded Linux
> > development, consulting, training and support.
> > http://free-electrons.com

On 08/22/12 02:39, Danomi Manchego wrote:
> What about sqlite?  According to http://www.sqlite.org/copyright.html, it is "public domain".  Should sqlite's license
> also be "sqlite license", or "public domain"?

  I'd use 'Public domain', it's a very specific and well-known legal term.  It
means the authors forfeit their copyright, and there are no restrictions whatsoever
on the use of the software.

  Regards,
  Arnout

Arnout Vandecappelle wrote:
> On 08/22/12 02:39, Danomi Manchego wrote:
>> What about sqlite?  According to 
>> http://www.sqlite.org/copyright.html, it is "public domain". Should 
>> sqlite's license
>> also be "sqlite license", or "public domain"?
>
>  I'd use 'Public domain', it's a very specific and well-known legal 
> term.  It
> means the authors forfeit their copyright, and there are no 
> restrictions whatsoever
> on the use of the software.

I agree with Arnout. "public domain" is much more informative, and is not
ambiguous.

Luca