summaryrefslogtreecommitdiffstats
path: root/meta/classes/utility-tasks.bbclass
Commit message (Collapse)AuthorAgeFilesLines
* utility-tasks.bbclass: miscellaneous fixKevin Tian2010-07-271-0/+3
| | | | | | | | Fix parse error with packages such as spectrum-fw whose name has no version string. Later we may have per-recipe option to disable automatic check for those known with troubles, to reduce complexity in this part. Signed-off-by Kevin Tian <kevin.tian@intel.com>
* utility-tasks.bbclass: add automatic version check for GIT/SVN protoKevin Tian2010-07-081-8/+64
| | | | | | | | | | | | both git/svn supports remote information query: 'git ls-remote', and 'svn info'. With them, now upstream version will be automatically checked for git/svn packages. In the meantime, manual latest version tagged in distro tracking fields are also compared as one alternative if upstream check fails. Also such check is one indicator whether tracking field is missing. Signed-off-by: Kevin Tian <kevin.tian@intel.com>
* utility-tasks.bbclass: automatic upstream version checkKevin Tian2010-06-031-0/+331
| | | | | | | | | | | | | | | | | 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>
* utility-tasks: Remove unneeded addtask parameterRichard Purdie2010-06-021-1/+1
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* do_distro_check: Recipe exists in other distros?Nitin A Kamble2010-06-021-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds a new task (distro_check) for each recipe. The task generates the source package list for Fedora OpenSuSE Ubuntu Debian & Mandriva Linux distros. As one recipe or source package can generate multiple target packages the recipe name is compared with the source package name list of LInux distributions. Thread locking is used to avoid multiple threads racing for the package list update. Then the recipe name (PN) is checked if it exists in the package list of distros. And if the DISTRO_PN_ALIAS then it is used to copmare pacakge_name instead of the PN variable. Just for example the DISTRO_PN_ALIAS can be defined in the recipe (.bb) files like this In the file xset_1.0.4.bb: DISTRO_PN_ALIAS = "Fedora=xorg-x11-server-utils;\ Ubuntu=x11-xserver-utils; Debian=x11-xserver-utils;Opensuse=xorg-x11" The final results are stored in the tmp/log/distro_check-${DATETIME}.result file. FYI this command will generate the results for all recipies: bitbake world -f -c distro_check Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
* utility-tasks.bbclass: Remove unneeded base_ prefix since we don't EXPORT ↵Richard Purdie2010-03-221-6/+6
| | | | | | these functions any longer Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* base.bbclass: Split up as per the patch in OE.dev by Chris Larson making ↵Richard Purdie2010-03-191-0/+97
code more readable and modularised Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>