Hi Belen, Alex Alex wrote: > Thus we collect the package information two times: once when the package is > build, and > once when the package is installed on the target. > Note that these two sets may not be identical, as on target install we > collect data for > a different set of packages that what was actually built during the current > run.
While the sets may not be identical, the dependency relation between packages should not change based on whether the package was from a previous build or from sstate. So, I would think the list of RDEPENDS to view always shows RDEPENDS and TRDEPENDS, whether a package was built, or pulled from sstate cache. Comments? Dave > -----Original Message----- > From: Damian, Alexandru [mailto:[email protected]] > Sent: Thursday, January 16, 2014 10:04 AM > To: Lerner, Dave > Cc: Eggleton, Paul ([email protected]); [email protected] > Subject: Re: TRDEPENDS, TRRECOMENDS vs RDEPENDS, RRECOMENDS > > Hi, > > > This is an artifact of how data is collected. > > > TRDEPENDS and TRECOMMENDS are just RDEPENDS and RRECOMMENDS collected at > target creation > time, instead of package build time. > > > What may happen is that for a target we use packages that were not built > during the > current build, but either in a previous build or reused from sstate cache. > > Thus we collect the package information two times: once when the package is > build, and > once when the package is installed on the target. > Note that these two sets may not be identical, as on target install we > collect data for > a different set of packages that what was actually built during the current > run. > > > I suggest that in "target install packages" page we show the T* dependencies, > and in the > "build packages" page we should the non-T dependencies. > > > Hope this helps, > Alex > > > > > On Wed, Jan 15, 2014 at 6:20 PM, Lerner, Dave <[email protected]> > wrote: > > > Hi Paul, Alex > > I have a question on inserts into the package_dependency and > target_installed_package. > > I would expect that for the following builds and sato in particular: > {core-image-minimal, qemux86} > {core-image-minimal, qemux86} > {core-image-sato, qemux86} > {[core-image-minimal,core-image-base], genericx86} > that there would be a few installed packages with some package > dependencies like > (RDEPENDS, RRECOMENDS), but that isn't the case. The only dependencies for > installed > packages are TRDEPENDS or TRRECOMMENDS. > > SELECT PkgS.name, PkgT.name dependsOn, PkgDep.dep_type > FROM orm_package PkgS, > orm_package_dependency PkgDep, > orm_package PkgT, > orm_target_installed_package Inst > WHERE > PkgS.id = PkgDep.package_id > AND PkgT.id = PkgDep.depends_on_id > AND Inst.package_id = PkgS.id > AND Inst.package_id = PkgDep.package_id > AND Inst.target_id = PkgDep.target_id > ; > name|dependsOn|dep_type > update-rc.d|busybox|6 > sysvinit-inittab|busybox|6 > libc6|busybox|6 > libc6|libc6|6 > packagegroup-core-boot|base-files|6 > packagegroup-core-boot|base-passwd|6 > ... > (more) > > adding a filter to the above to filter out the "T..." types > AND PkgDep.dep_type < 6 > returns an empty set. > > What is the meaning of TRDDEPENDS and TRRECOMMENDs and do the results > seem correct? > > Thanks > Dave > > > > > > -- > > Alex Damian > Yocto Project > > SSG / OTC _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
