From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: Design Document of "Yocto 1656 Recipe creation/import script"
Date: Fri, 06 Jan 2012 11:18:59 -0800 [thread overview]
Message-ID: <4F074923.7030402@linux.intel.com> (raw)
In-Reply-To: <4F06C43D.3090102@windriver.com>
Hi Kai,
On 06/01/12 01:51, Kang Kai wrote:
> This is the design document of "Yocto 1656 Recipe creation/import
> script". Please help to review it.
> Any suggestion is appreciate.
You should check out autospectacle[1] that I linked to in the bug
report. It does a lot of guessing using clever tricks like searching
Freshmeat, doap files, READMES etc to get a description[2] and analysing
configure.ac[3], qmake[4], etc. to determine dependencies.
The autospectacle perl script is reasonably well commented and quite
readable.
I'm not suggesting we adopt all of the features in it but many of them
are useful techniques for this effort.
Regards,
Joshua
1. https://meego.gitorious.org/meego-developer-tools/autospectacle/
2.
https://meego.gitorious.org/meego-developer-tools/autospectacle/blobs/master/autospectacle.pl#line1001
3.
https://meego.gitorious.org/meego-developer-tools/autospectacle/blobs/master/autospectacle.pl#line633
4.
https://meego.gitorious.org/meego-developer-tools/autospectacle/blobs/master/autospectacle.pl#line840
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-01-06 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 9:51 Design Document of "Yocto 1656 Recipe creation/import script" Kang Kai
2012-01-06 14:18 ` 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 [this message]
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=4F074923.7030402@linux.intel.com \
--to=josh@linux.intel.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.