Martin Jansa <[email protected]> writes: > > On Fri, Jan 15, 2010 at 08:46:24AM +0100, Jens Seidel wrote: > > On Thu, Jan 14, 2010 at 06:14:09PM +0100, Martin Jansa wrote: > > > > > > libbz2 is dependency of bzip2 and opkg wants to upgrade it > > > first.. but in that time there is still bzip2 with libbz > > > included on filesystem. Not sure how to fix this properly :/. > > > > Let libbz conflict with bzip2 <= 1.0.5-r0.4 would not work? I have to read > > more about OpenEmbedded ... > > It would but bitbake doesn't support versioned dependencies, so I guess > there is no way to specify version in RCONFLICTS :/.
What does that mean--what does bitbake even have to do with it? Isn't all of the logic that creates a .ipk from a bitbake recipe implemented in bbclass files in OE (on top of bitbake), which ultimately just call out to the ipkg command-line tools? So, can't you just write "bzip2 (<= 1.05-r0.4)" in RCONFLICTS, and have bitbake just naively pass that string all the way through to ipkg-build? > Not sure about .opk files maybe they support it in headers. Yes--the Debian package format supports it, and there appears to be code in opkg to handle it; cf. libopkg/pkg_depends.c, libopgk/pkg_depends.h. -- "Don't be afraid to ask (λf.((λx.xx) (λr.f(rr))))." _______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
