| Summary: | Document the method to prune sstate-cache of old entries | ||
|---|---|---|---|
| Product: | [Documentation] Development Manual | Reporter: | Yoann Congal <yoann.congal> |
| Component: | development | Assignee: | Michael Opdenacker <michael.opdenacker> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | jester, randy.macleod, richard.purdie, yoann.congal |
| Version: | unspecified | ||
| Target Milestone: | 4.3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Yoann Congal
2023-08-04 10:54:55 UTC
I'm missing something... What's the added value of the suggested command... find $SSTATE -type f -atime +$DAYS -delete ... when the docs already suggest to use: sstate-cache-management.sh --remove-duplicated --cache-dir=build/sstate-cache This documented and dedicated command seems to do the job. How is the above "find" command different or better? I suspect but haven't recently confirmed that it's simply much, much faster. If you don't have a big sstate-cache tree around to make copies of and confirm this assertion, let me know. |