Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] LICENSE fields and packages
Date: Wed, 26 Nov 2008 11:38:58 +0100	[thread overview]
Message-ID: <ggj902$7j2$1@ger.gmane.org> (raw)
In-Reply-To: <200811261011.09918.openembedded@haerwu.biz>

On 26-11-08 10:11, Marcin Juszkiewicz wrote:
> Tuesday 25 of November 2008 22:57:27 Koen Kooi napisał(a):
>> On 25-11-08 22:42, Marcin Juszkiewicz wrote:
>>> Tuesday 25 of November 2008 22:02:00 Koen Kooi napisał(a):
>
>>>> The concrete problem I have is that I have a bunch of licenses
>>>> that don't have a name (not even inside the company that wrote
>>>> them), so my recipes have things like
>>>>
>>>> LICENSE = "proprietary binary"
>>>> LICENSE = "evil binary"
>>> So add license.txt into /usr/share/doc/${PN}/ with content of that
>>> package license. I have done few such packages during last year as
>>> some copyright holders gave permissions to distribute their stuff
>>> *ONLY* with attached license. This kind of stuff does not even need
>>> nothing new - it is just another file in SRC_URI.
>
>> I like that idea very much, but the license file will have to be in
>> every entry in PACKAGES, so ${PN} won't work. Do you have a
>> suggestion on how to handle that?
>
> ${PN}-license package on which all entries from PACKAGES will RDEPEND?

That doesn't put the license in the packages itself, so if I give you 
evil-binary_1.0_armv7a.ipk you still don't know what the license is.

What about a bbclass that iterates over every entry in PACKAGES and puts 
the license in ${datadir}/<pkgname>/LICENSE.txt?

regards,

Koen


>>>> So as short term solution I'd like to be able to point to a url
>>>> for the 'licenses without a proper name'
>>> Yeah.. especially when license contents is available only in
>>> restricted area for which simple person can not get access (for
>>> example Marvell extranet). If there are packages which have own
>>> license then such license should be inside of package.
>> So you agree that in those situations we can point to an URL, but in
>> other cases either use the name or include it in the package?
>
> No, I mean that if license is not one of popular ones covered by
> base-files-doc or common-licenses package it should be added into OE
> metadata. Ok, it can be a bit of overkill adding all those 'povray',
> 'openssl' etc licenses but when we will end then it will be clear how
> each recipe is licensed.
>
> Regards,





  reply	other threads:[~2008-11-26 10:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25 19:26 [RFC] LICENSE fields and packages Koen Kooi
2008-11-25 19:54 ` Richard Purdie
2008-11-25 20:40   ` Koen Kooi
2008-11-25 20:13 ` Marcin Juszkiewicz
2008-11-25 21:02   ` Koen Kooi
2008-11-25 21:42     ` Marcin Juszkiewicz
2008-11-25 21:57       ` Koen Kooi
2008-11-26  9:11         ` Marcin Juszkiewicz
2008-11-26 10:38           ` Koen Kooi [this message]
2008-11-26 11:21           ` Koen Kooi
2008-11-26 11:31             ` Phil Blundell
2008-11-26 12:27               ` Koen Kooi
2008-11-26 13:57                 ` Phil Blundell
2008-11-26 14:18                   ` Koen Kooi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='ggj902$7j2$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox