Re: [ptxdist] Regenerate license report
On Wed, Apr 19, 2023 at 09:28:02AM +0200, Guillermo Rodriguez Garcia wrote: > El miércoles, 19 de abril de 2023, Michael Olbrich > escribió: > > On Tue, Apr 18, 2023 at 05:18:58PM +0200, Guillermo Rodriguez Garcia wrote: > > > El mar, 18 abr 2023 a las 16:37, Guillermo Rodriguez Garcia (< > > > guille.rodrig...@gmail.com>) escribió: > > > > Is there a way to force ptxdist to regenerate a license-report after it > > > > has been generated already with "ptxdist make license-report" ? > > > > > > > > I didn't find any "clean" rule for this, and the naive approach of just > > > > deleting the platform-xxx/report dir doesn't work (trying to run > > ptxdist > > > > make license-report after this results in errors). > > > > > > > > > > The best I have found is: > > > > > > rm -rf platform-xxx/report > > > rm platform-xxx/state/*.report > > > > > > But I assume there is a cleaner way :-) > > > > That depends a bit on why you want to regenerate the report. If you need to > > regenerate the per package stuff in platform-xxx/report/ then removing > > platform-xxx/state/*.report is the way to go. If that part remains > > unchanged, then just removing the pdfs should be enough. > > > This was because of adjustments to license info in the .make files so I > guess I need to remove the .report files :-) > > Thank you for the response, If you change a .make file, then that should be detected automatically and the license info for that package should be regenerated automatically. It should not be necessary to do anything manually. Michael -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- |
Re: [ptxdist] Regenerate license report
El miércoles, 19 de abril de 2023, Michael Olbrich escribió: > Hi, > > On Tue, Apr 18, 2023 at 05:18:58PM +0200, Guillermo Rodriguez Garcia wrote: > > El mar, 18 abr 2023 a las 16:37, Guillermo Rodriguez Garcia (< > > guille.rodrig...@gmail.com>) escribió: > > > Is there a way to force ptxdist to regenerate a license-report after it > > > has been generated already with "ptxdist make license-report" ? > > > > > > I didn't find any "clean" rule for this, and the naive approach of just > > > deleting the platform-xxx/report dir doesn't work (trying to run > ptxdist > > > make license-report after this results in errors). > > > > > > > The best I have found is: > > > > rm -rf platform-xxx/report > > rm platform-xxx/state/*.report > > > > But I assume there is a cleaner way :-) > > That depends a bit on why you want to regenerate the report. If you need to > regenerate the per package stuff in platform-xxx/report/ then removing > platform-xxx/state/*.report is the way to go. If that part remains > unchanged, then just removing the pdfs should be enough. This was because of adjustments to license info in the .make files so I guess I need to remove the .report files :-) Thank you for the response, Guillermo -- Guillermo Rodriguez Garcia guille.rodrig...@gmail.com
Re: [ptxdist] Regenerate license report
Hi, On Tue, Apr 18, 2023 at 05:18:58PM +0200, Guillermo Rodriguez Garcia wrote: > El mar, 18 abr 2023 a las 16:37, Guillermo Rodriguez Garcia (< > guille.rodrig...@gmail.com>) escribió: > > Is there a way to force ptxdist to regenerate a license-report after it > > has been generated already with "ptxdist make license-report" ? > > > > I didn't find any "clean" rule for this, and the naive approach of just > > deleting the platform-xxx/report dir doesn't work (trying to run ptxdist > > make license-report after this results in errors). > > > > The best I have found is: > > rm -rf platform-xxx/report > rm platform-xxx/state/*.report > > But I assume there is a cleaner way :-) That depends a bit on why you want to regenerate the report. If you need to regenerate the per package stuff in platform-xxx/report/ then removing platform-xxx/state/*.report is the way to go. If that part remains unchanged, then just removing the pdfs should be enough. Michael -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- |
Re: [ptxdist] ptx/image-install for older ptxdist releases
Hi, On Tue, Apr 18, 2023 at 04:39:54PM +0200, Guillermo Rodriguez Garcia wrote: > I have an "image" package that generates more than one image file. > > In the past I asked what would be the best way to handle this so that the > clean target works correctly. Michael suggested to use ptx/image-install: > > > You should be able to use ptx/image-install in the image rule. Just like > > regular packages. File installed with this are recorded and later removed > > in the clean stage. > > I have found that ptx/image-install indeed solves the problem when > available; however this was added relatively recently and does not exist > for older ptxdist releases. > > Is there a way to achieve similar functionality in ptxdist releases where > ptx/image-install is not available ? It should be possible to backport that feature. Take a look at the commit that introduced the feature 3694633183ae70aeba062d53db3eeb4bf521d090. You basically need to copy that stuff into your BSP in the same locations (rules/post and scripts/lib). Michael -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- |
