openembedded-core.git/meta/classes/package_deb.bbclass, branch danny Mirror of openembedded-core classes: Update to use corrected bb.utils.explode_dep_versions2 API 2012-10-02T10:37:10+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2012-10-02T10:37:07+00:00 16a892431d0c0d03f8b561b92909cf2f11af4918 The bb.utils.explode_dep_versions function has issues where dependency information can be lost. The API doesn't support maintaining the correct information so this changes to use a new function which correctly handles the data. This patch also fixes various points in the code to ensure that we do not have any duplicates in things that use explode_dep_versions. A new sanity test to test the contents of the R* variables is also added. [Some changes from Mark Hatle <mark.hatle@windriver.com>] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
The bb.utils.explode_dep_versions function has issues where dependency information
can be lost. The API doesn't support maintaining the correct information so this
changes to use a new function which correctly handles the data.

This patch also fixes various points in the code to ensure that we do not have any
duplicates in things that use explode_dep_versions.

A new sanity test to test the contents of the R* variables is also added.

[Some changes from Mark Hatle <mark.hatle@windriver.com>]

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
package_deb/ipk: Remap < and > to << and >> 2012-10-02T10:16:10+00:00 Mark Hatle mark.hatle@windriver.com 2012-09-30T00:19:11+00:00 bbcc78d8ff03725ce5b3b65ce24025c3da45f2ab In deb and ipk, < means <=, while > means >=... there is a different operator << and >> that means < and >, so we map them when constructing the packages. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
In deb and ipk, < means <=, while > means >=... there is a different
operator << and >> that means < and >, so we map them when constructing
the packages.

Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Replace "echo -e" with "printf" to have the same behavior in dash or bash 2012-09-20T12:18:19+00:00 Andrei Gherzan andrei@gherzan.ro 2012-09-20T09:56:59+00:00 a19880ad10ccb5d7d909dcf9de5c3dc58a0ebcd3 oe-core removed the prerequisite to have sh as bash. POSIX doesn't define any options and furthermore allows 'echo -e' to be the default behavior. This means that in dash 'echo -e' will actually print '-e' and interpret backslashes by default. We use instead 'printf' builtin command with or without '\n' to simulate 'echo -e' or 'echo -n'. 'printf' needs format while 'echo' can be used without any arguments. So 'echo >' was replaced by 'printf "" >'. 'echo' without '-n' flag adds a new line by default so to keep the same behavior of two new lines while using 'echo "\n"', 'printf "\n\n"' is used. [YOCTO #3138] Signed-off-by: Andrei Gherzan <andrei@gherzan.ro> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
oe-core removed the prerequisite to have sh as bash. POSIX doesn't define
any options and furthermore allows 'echo -e' to be the default behavior.
This means that in dash 'echo -e' will actually print '-e' and interpret
backslashes by default. We use instead 'printf' builtin command with or
without '\n' to simulate 'echo -e' or 'echo -n'.
'printf' needs format while 'echo' can be used without any arguments. So
'echo >' was replaced by 'printf "" >'.
'echo' without '-n' flag adds a new line by default so to keep the same
behavior of two new lines while using 'echo "\n"', 'printf "\n\n"' is
used.

[YOCTO #3138]

Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
classes/package_deb: add PackageArch field 2012-07-26T13:39:49+00:00 Paul Eggleton paul.eggleton@linux.intel.com 2012-07-23T21:42:26+00:00 3f4f6726646e18ae21919e2f361b669332796aef If we want to query the PACKAGE_ARCH from the installed package (as we do in order to be able to do a pkgdata lookup for example) then we need to have this stored in its own field as this is not always the same as the Architecture field for deb packages. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> 
If we want to query the PACKAGE_ARCH from the installed package (as we
do in order to be able to do a pkgdata lookup for example) then we need
to have this stored in its own field as this is not always the same as
the Architecture field for deb packages.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Convert tab indentation in python functions into four-space 2012-07-19T09:17:30+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2012-07-11T17:33:43+00:00 604d46c686d06d62d5a07b9c7f4fa170f99307d8 Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fix manual log file paths 2012-07-03T07:05:29+00:00 Mark Hatle mark.hatle@windriver.com 2012-06-18T21:42:45+00:00 779db325d407f0bade84572ef99fdad4d0c88011 When a recent change, the path to log files may be contained within an arbitrary directory. To generate the manual log files in the correct path we should be using the ${BB_LOGFILE}'s path instead of always assuming the logs go into ${WORKDIR}/temp. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> 
When a recent change, the path to log files may be contained within an
arbitrary directory.  To generate the manual log files in the correct path
we should be using the ${BB_LOGFILE}'s path instead of always assuming the
logs go into ${WORKDIR}/temp.

Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
package_deb: When searching for E:, anchor expression 2012-07-02T15:44:49+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2012-06-29T15:51:22+00:00 8f4e160ce0b0c755545d62b06db14decd45b9f1e If we don't do this it will match on expressions like "NOTE:" which are not fatal errors. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
If we don't do this it will match on expressions like "NOTE:" which
are not fatal errors.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta: replace os.system with subprocess.call 2012-05-30T09:56:15+00:00 Robert Yang liezhi.yang@windriver.com 2012-05-29T14:53:06+00:00 a07d03cc6f67c88feb9813ae7deb6e4a93552dfe Replace os.system with subprocess.call since the older function would fail (more or less) silently if the executed program cannot be found More info: http://docs.python.org/library/subprocess.html#subprocess-replacements [YOCTO #2454] Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Replace os.system with subprocess.call since the older function would
fail (more or less) silently if the executed program cannot be found

More info:
http://docs.python.org/library/subprocess.html#subprocess-replacements

[YOCTO #2454]

Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
package.bbclass: Drop EXPORT_FUNCTIONS use against mapping_rename_hook 2012-05-11T17:03:26+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2012-05-10T08:24:22+00:00 74daad03ca29a03b0005f7d2b90a0347d5b583a5 The usage of this function renaming and it being called using bb.build.exec_func() causes needless indirection loops, confusing log files and seems generally pointless. This simplification makes the process much simpler and faster. I can't come up with a good reason why the export_functions functionality is needed for this function. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
The usage of this function renaming and it being called using
bb.build.exec_func() causes needless indirection loops, confusing log
files and seems generally pointless.

This simplification makes the process much simpler and faster. I can't
come up with a good reason why the export_functions functionality is
needed for this function.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
classes/package_deb: create .gz index instead of .bz2 2012-04-11T09:58:16+00:00 Paul Eggleton paul.eggleton@linux.intel.com 2012-04-10T22:52:23+00:00 518f4af617f91b209086acb51454393147aa92dd apt is looking for Packages.gz files instead of the .bz2 files we are currently creating and failing when they cannot be found. It is not immediately obvious how to make the current version use the .bz2 indexes; thus create .gz indexes for now which allows us to successfully create images. Tested on both a Fedora 14 and an Ubuntu 11.10 host machine. Fixes [YOCTO #1858]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
apt is looking for Packages.gz files instead of the .bz2 files we are
currently creating and failing when they cannot be found. It is not
immediately obvious how to make the current version use the .bz2
indexes; thus create .gz indexes for now which allows us to
successfully create images.

Tested on both a Fedora 14 and an Ubuntu 11.10 host machine.

Fixes [YOCTO #1858].

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>