diff options
| author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-04-07 17:33:21 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-04-10 08:31:17 +0100 |
| commit | 21f0318abc5c0405d134ac4bbb8ed9b9294fc17d (patch) | |
| tree | fba898730a7b4db7d9dd3cbab5e85bf62bfecb8d /meta/recipes-bsp/efivar/efivar | |
| parent | 3d4e5a0b7fdf1d17d308bc1fa7752f934b5b91e5 (diff) | |
| download | poky-21f0318abc5c0405d134ac4bbb8ed9b9294fc17d.tar.gz | |
package_ipk/deb: Fix specific version handling
We recently added a "xxx (= 1.2.3)" style dependency to a recipe and have
been having trouble with the opkg and debian backends with it.
The issues is that for debian, "=" really does mean equals and includes the
PR field. One bitbake recipe does not know the PR of another, nor shoud it.
In other words 1.2.3 != 1.2.3-r0. Debian defaults to a PR of "0", not our
"r0".
The only way I can think of to make this work is to change "=" dependencies
without revision information (no "-r" in the version) into things like:
"xxx (>= 1.2.3), xxx (<< 1.2.3.0)". This appears to work even if it is a
pretty horrible workaround.
(From OE-Core rev: 3ba177a1b8e553716f45606aa65b0a74e55d94c1)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-bsp/efivar/efivar')
0 files changed, 0 insertions, 0 deletions