| Summary: | Add possibility of dumping depsig.* from sstate-cache | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Jacob Kroon <jacob.kroon> |
| Component: | Scripts and Tools | Assignee: | Jacob Kroon <jacob.kroon> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | randy.macleod, ross.burton |
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Jacob Kroon
2022-06-23 05:28:48 UTC
Hi Jacob, We don't think that many people have this requirement. Please either send a patch or specify why others should be interested as well as exactly want needs to be done. Thanks! (In reply to comment #1) > Hi Jacob, > > We don't think that many people have this requirement. > Who are "we" ? > Please either send a patch or specify why others should be interested as > well as exactly want needs to be done. > I tried to explain the reason in the bug description. Which part of it do "you" think is unclear ? I am building with TMPDIR on a tmpfs, so it gets wiped everytime I reboot. Hence the need to extract "current" depsig.* files, in order to compare what changed. Hi Jacob, I should have explained in my comment but the 'we' in that context refers to the people who attend the weekly Yocto bug triage (mentioned here: https://www.yoctoproject.org/public-virtual-meetings/ ). There can be quite a few issues to look at each week so I can be quite rushed when replying. I'll try to remember to add a signature such as '-- YP bug review team', so that people know who 'we' are. You are welcome to join this meeting. I don't recall the conversation now but I suspect that Richard Purdie and Joshua Watt talked about it and I typed. I see that you also brought the topic up here: https://lists.openembedded.org/g/openembedded-architecture/topic/90726763#1532 so for now, I'm not sure what to suggest. Having this enhancement open will mean that the issue gets reviewed at every 2 years if no one picks up the issue because we look at all issues that are >= 2 years old on this list: https://wiki.yoctoproject.org/wiki/Bug_Triage#Future_.26_4.99_Milestones in each meeting. I know that isn't helpful to you right now but without more participants sending patches, the project members are doing all they can to keep recipes current and to fix critical issues. Ok, thank you for clarifying. If Richard and Joshua agree it is low priority then fine, I'll see if I can get it implemented. |