From: Harvey C. <hch...@3g...> - 2012-03-22 22:33:10
|
I too have rarely ever had an OE build from scratch succeed without a 404. So, I keep a cached copy of all of my downloads to seed new builds. However, sometimes I build some package temporarily or remove something we no longer use, but I know the source files are still in my downloads directory. Is there a way to clean up that directory to only the necessary dependencies? |
From: Simon K. <sim...@pg...> - 2012-03-25 21:13:51
|
On 23/03/2012, at 11:33 AM, Harvey Chapman wrote: > I know the source files are still in my downloads directory. Is there a way to clean up that directory to only the necessary dependencies? I haven't seen any way to do that built in to OE/bitbake. My only thought would be to run `bitbake -g my-image` to generate the dependency graphs, use the resulting graphviz file to get a list of dependent packages, then clean up your sources based on that. If you decide to go with this approach, Scott Ellis has a tool for parsing the dependency graphs at https://github.com/scottellis/oe-deptools. Simon. |
From: Harvey C. <hch...@3g...> - 2012-03-25 21:21:07
|
On Mar 25, 2012, at 5:13 PM, Simon Knopp wrote: > On 23/03/2012, at 11:33 AM, Harvey Chapman wrote: > >> I know the source files are still in my downloads directory. Is there a way to clean up that directory to only the necessary dependencies? > > I haven't seen any way to do that built in to OE/bitbake. My only thought would be to run `bitbake -g my-image` to generate the dependency graphs, use the resulting graphviz file to get a list of dependent packages, then clean up your sources based on that. > > If you decide to go with this approach, Scott Ellis has a tool for parsing the dependency graphs at https://github.com/scottellis/oe-deptools. Thanks for the hint. I was kind of hoping that there would be a backup sources folder option for OE that it could pull from. I thought of trying to be clever by doing a full build and looking at access times. I also thought of doing a full build, but only up to the unpack step and either filtering the output or starting with an empty sources folder and fixing it as I go which would be tedious. |