Hello, i was working with bitbake for cross building file system images for an embedded project. in this setup i was updating a bigger package to a more recent version. for some reasons it created noticeable fewer packages for me leading to the state that bitbake simply kept the corresponding result packages from an older not-really-matching version from a prior build attempt in place.
for the reason of using a probably working pair of tools and recipes i was doing my tasks using an older version of bitbake (1.8.12). (surely there is 1.8.18 and 1.10.0 available to me but i just did not check that versions sufficiently for now.) my short term work-around was this: i was manually sending the old packages to the morgue and then started researching reasons for the changed package build results. later packages should now be in state to fault when something is missing instead of being inadequately served by something older. the first case is desirable, the later feels buggy. does someone know how bitbake should behave in cases where a newer recipe version does no longer produce a certain package since no files were installed by the build? does that further mean an ever added results package must stay in the recipe for an indefinitely long period even if it will be empty just for forced removal? if that scenario is already addressed by some patch then please drop me a note on the current state. regards, Alex. -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail _______________________________________________ Bitbake-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bitbake-dev
