Please, ignore the last patch... it was completely wrong...
But please someone help me on this issue...
I've noticed that my problem is not the way that bitbake gets the
RDEPENDS and RRECOMENDS, but
-dev and -dbg packages rdepends and rrecommends the package itself and
when trying to get the preferred provider it gets the preferred
(defined by PREFERRED_VERSION) or the latest... but it is completely
wrong when your are building a required version directly from bitbake
command line, e.g. $ bitbake bash-3.0
Actually what I believe that is wrong is the creating of the cyclic
dependency. ( bitbake bash-3.0 depends on bash-dev that depends on
bash that by default is the latest(bash-3.2)).
So, my idea is to avoid add your self to your rdepends and rrecommends list.
Please, check out this patch:
Index: bitbake/lib/bb/cache.py
===================================================================
--- bitbake.orig/lib/bb/cache.py 2008-05-05 20:04:21.000000000 -0300
+++ bitbake/lib/bb/cache.py 2008-05-05 20:04:28.000000000 -0300
@@ -365,8 +365,10 @@
if not package in cacheData.runrecs[file_name]:
cacheData.runrecs[file_name][package] = []
- cacheData.rundeps[file_name][package] = rdepends + " " +
(self.getVar("RDEPENDS_%s" % package, file_name, True) or "")
- cacheData.runrecs[file_name][package] = rrecommends + " "
+ (self.getVar("RRECOMMENDS_%s" % package, file_name, True) or "")
+ rrdepends_pkg = self.getVar("RDEPENDS_%s" % package,
file_name, True) or ""
+ cacheData.rundeps[file_name][package] = "%s %s" %
(rdepends,pn not in rrdepends_pkg and rrdepends_pkg or "")
+ rrecommends_pkg = self.getVar("RRECOMMENDS_%s" % package,
file_name, True) or ""
+ cacheData.runrecs[file_name][package] = "%s %s" %
(rrecommends, pn not in rrecommends_pkg and rrecommends_pkg or "")
# Collect files we may need for possible world-dep
# calculations
//EOF
what do you think?
Best Regards,
vivijim
On Thu, May 1, 2008 at 7:01 PM, Rodrigo Vivi <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> since the bugtracker is down, I'm going to send here a patch
> (attached) that fixes this problem:
>
> When you explicitly build a version using
> $ bitbake package-version
> bitbake erroneously adds the package itself to rdepends and
> rrecommends list. After that when it tries to fix unresolved packages
> it looks for the PREFERRED_VERSION or the latest one completely
> ignoring the asked version.
>
> Cheers,
> vivijim
>
>
>
> On Tue, Apr 29, 2008 at 6:46 PM, Rodrigo Vivi <[EMAIL PROTECTED]> wrote:
> > I forgot to say that I've already read this message:
> >
> > "This usually means one provides something the other doesn't and should."
> >
> > but it is happening even for identical bb (with different versions)
> > too. I mean, even when they are providing exactly the same thing.
> >
> >
> >
> > On Tue, Apr 29, 2008 at 6:11 PM, Rodrigo Vivi <[EMAIL PROTECTED]> wrote:
> > > Hi there,
> > >
> > > I've noticed that when I try to build directly an old version of a
> > > package that doesn't have a PREFERRED_VERSION defined,
> > > e.g. bitbake bash-3.0, my bitbake (1.8.11) build both: bash-3.0
> > > (asked) and bash-3.2 (latest).
> > >
> > > is it a bug? a issue? or am I doing something wrong (supid?)
> > >
> > > Thanks in advance
> > > Regards
> > >
> > > --
> > > Rodrigo Vivi
> > > INdT - Instituto Nokia de Tecnologia
> > > Blog: http://blog.vivi.eng.br
> > > GPG: 0x905BE242 @ wwwkeys.pgp.net
> > >
> >
> >
> >
> > --
> > Rodrigo Vivi
> > INdT - Instituto Nokia de Tecnologia
> > Blog: http://blog.vivi.eng.br
> > GPG: 0x905BE242 @ wwwkeys.pgp.net
> >
>
>
>
> --
>
>
> Rodrigo Vivi
> INdT - Instituto Nokia de Tecnologia
> Blog: http://blog.vivi.eng.br
> GPG: 0x905BE242 @ wwwkeys.pgp.net
>
--
Rodrigo Vivi
INdT - Instituto Nokia de Tecnologia
Blog: http://blog.vivi.eng.br
GPG: 0x905BE242 @ wwwkeys.pgp.net
_______________________________________________
Bitbake-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bitbake-dev
