diff options
| author | Kevin Tian <kevin.tian@intel.com> | 2010-05-30 19:14:24 +0800 |
|---|---|---|
| committer | Richard Purdie <rpurdie@linux.intel.com> | 2010-06-03 12:23:22 +0100 |
| commit | 3161c9b15a39e552b383c704851edead8435365c (patch) | |
| tree | f04cfa1b1e91eb7b7779f3920f4b692ffae3bf59 /meta/packages/startup-notification | |
| parent | 50224b5afa19c9e68fc36d9a44f3f39e8f0da225 (diff) | |
| download | openembedded-core-3161c9b15a39e552b383c704851edead8435365c.tar.gz openembedded-core-3161c9b15a39e552b383c704851edead8435365c.tar.bz2 openembedded-core-3161c9b15a39e552b383c704851edead8435365c.tar.xz openembedded-core-3161c9b15a39e552b383c704851edead8435365c.zip | |
utility-tasks.bbclass: automatic upstream version check
Automatic upstream version check can be triggered by "bitbake xxx -c checkpkg".
The rationale behind is to find a automatic way for version comparison between
current in-use one and upstream progress. The tricky thing is how to find out
useful version string from mass diverse information. Fortunately now it mostly
work for wget based protocol, except some sites (e.g. sourceforge) not providing
a directory service. Repo (git/svn/cvs) based protocols are handled in a very
simple manner, by always tagging as update required. This will be further
improved later. Use 'world' target to retrieve a full version check for all
active recipes.
Along with version check, other package information is also collected from
existing fields in .bb file
Signed-off-by Kevin Tian <kevin.tian@intel.com>
Diffstat (limited to 'meta/packages/startup-notification')
0 files changed, 0 insertions, 0 deletions