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-09 22:51:12 +0100 |
| commit | 3ba177a1b8e553716f45606aa65b0a74e55d94c1 (patch) | |
| tree | 7be2cb01acb17a50f359ccbd711c6f38dc165021 /LICENSE.GPL-2.0-only | |
| parent | e3da4da7e5da5bb9e1d360e2be2fdd5132e69320 (diff) | |
| download | openembedded-core-contrib-3ba177a1b8e553716f45606aa65b0a74e55d94c1.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.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'LICENSE.GPL-2.0-only')
0 files changed, 0 insertions, 0 deletions