From: Joshua Lock <josh@linux.intel.com>
To: poky@yoctoproject.org
Subject: Re: [PATCH 1/1] create-recipe: create a recipe from source URI
Date: Mon, 27 Feb 2012 15:40:08 -0800 [thread overview]
Message-ID: <4F4C1458.9040800@linux.intel.com> (raw)
In-Reply-To: <05007499a51a6cdeb40dfe66b0d8ea60df08c048.1329470296.git.kai.kang@windriver.com>
On 17/02/12 01:28, Kang Kai wrote:
> This feature is from Yocto 1.2 Bug 1656. create-recipe allows you
> to give an upstream URL then generate a recipe file. It trys to check
> source URI, license files, configure files, rpm spec file .etc to
> get package name, version, description, summary, license and license
> file, build dependecy and so on.
This works pretty well based on a few tests here but as this is a
heavily derived work of a GPLv2 script (IANAL) I'm pretty sure we need
to respect the author of the original works copyright and license.
In concrete terms I expect we need to:
* use the original license header WITH the original Intel 2010 copyright
* add Wind River's copyright to the new code
* mention and link to the original work in a comment in the script
With those changes I expect we can merge this and iterate on it as
people use it.
Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-02-27 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 9:25 [PATCH 0/1] Yocto 1656: Recipe creation/import script Kang Kai
2012-02-17 9:28 ` [PATCH 1/1] create-recipe: create a recipe from source URI Kang Kai
2012-02-17 10:15 ` Andrei Gherzan
2012-02-27 23:40 ` Joshua Lock [this message]
2012-02-28 1:48 ` Kang Kai
2012-02-28 1:55 ` Joshua Lock
2012-02-28 1:58 ` Kang Kai
2012-02-21 17:12 ` [PATCH 0/1] Yocto 1656: Recipe creation/import script Saul Wold
2012-02-22 1:51 ` Kang Kai
-- strict thread matches above, loose matches on Subject: below --
2012-03-01 6:06 [PATCH 0/1] V3: " Kang Kai
2012-03-01 6:17 ` [PATCH 1/1] create-recipe: create a recipe from source URI Kang Kai
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=4F4C1458.9040800@linux.intel.com \
--to=josh@linux.intel.com \
--cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.