From: Kang Kai <Kai.Kang@windriver.com>
To: <yocto@yoctoproject.org>
Subject: Design Document of "Yocto 1656 Recipe creation/import script"
Date: Fri, 6 Jan 2012 17:51:57 +0800 [thread overview]
Message-ID: <4F06C43D.3090102@windriver.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 163 bytes --]
Hi All,
This is the design document of "Yocto 1656 Recipe creation/import
script". Please help to review it.
Any suggestion is appreciate.
Regards,
Kai
[-- Attachment #2: recipe_creation_bb.txt --]
[-- Type: text/plain, Size: 906 bytes --]
Design documnet for Recipe creation/import script
* Purpose
The feature is from Yocto 1.2 Bug 1656. A script or similar system
that would allow you to give is an upstream URL, tarball, patch set,
package (SRPM, or debian style) and generate a recipe based on those
instructions.
Name it with bitbake-createbb, and integrate into the build system
to use the build system infrastructure that similiar with bitbake-runtask.
* Usage:
bitbake-createbb <SRC_URI> [PATCH_SRC_URI]
* Steps
1 download the source package frowm the SRC_RUI
2 get package name and version from package or tarball name.
3 get summary and description from SRPM spec file or debian control file, or from configure files.
4 get license and license checksum.
5 get dependent packages
|-- just parse spec file or debian control file
|-- or get them by parse configure files
6 remove downloaded files
next reply other threads:[~2012-01-06 9:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 9:51 Kang Kai [this message]
2012-01-06 14:18 ` Design Document of "Yocto 1656 Recipe creation/import script" Andreas Müller
2012-01-09 3:27 ` Kang Kai
2012-01-06 14:35 ` Pedro Algarvio
2012-01-09 3:30 ` Kang Kai
2012-01-09 6:02 ` Kang Kai
2012-01-06 19:18 ` Joshua Lock
2012-01-09 5:49 ` Kang Kai
2012-01-09 21:31 ` Joshua Lock
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=4F06C43D.3090102@windriver.com \
--to=kai.kang@windriver.com \
--cc=yocto@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.