On Thu, 21 Sept 2023 at 16:39, chris.lapla...@agilent.com <chris.lapla...@agilent.com> wrote:
> That is very impressive and I'd also love to hear about what heuristics it > uses. It's actually rather simple. It uses glob.glob on stamps in tmp/, then on local sstate to find possible matches, then sorts them by mtime and takes the most recent. It's what would work most of the time, but we could add printdiff-all (print difference with all sstate matches) or printdiff-N (N most recent). It also could abstain from dumping locked-sigs.inc into cwd with both -S none and -S printdiff, unless explicitly asked I just discovered there's also scripts/bitbake-whatchanged (that hasn't seen activity in years and is neither documented nor tested). Unsurprisingly then, it doesn't work in the same scenario: ================ alex@Zen2:/srv/storage/alex/yocto/build-sstate$ bitbake-whatchanged libsolv-native Figuring out the STAMPS_DIR ... Generating the new stamps ... (need several minutes) === Summary: (0 changed, 0 unchanged) Newly added: 0 PV changed: 0 PR changed: 0 Dependencies changed: 0 Removing the newly generated stamps dir ... ================ Maybe this is what RP was referring to when he said the tools don't work properly? Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61077): https://lists.yoctoproject.org/g/yocto/message/61077 Mute This Topic: https://lists.yoctoproject.org/mt/101503345/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
