mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
* Re: [ptxdist] Regenerate license report
       [not found] ` <CABDcavbWjKNGU83TJrGJf1SroL_dThjGw0utU=vhvw6+t3x8=w@mail.gmail.com>
@ 2023-04-19  7:23   ` Michael Olbrich
       [not found]     ` <CABDcavach4LT-_LcLvnGY5tzr0ungz0pAnNbSLJgwFf-xS1MPw@mail.gmail.com>
  0 siblings, 1 reply; 3+ messages in thread
From: Michael Olbrich @ 2023-04-19  7:23 UTC (permalink / raw)
  To: Guillermo Rodriguez Garcia; +Cc: ptxdist

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.rodriguez@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-5555 |



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [ptxdist] Regenerate license report
       [not found]     ` <CABDcavach4LT-_LcLvnGY5tzr0ungz0pAnNbSLJgwFf-xS1MPw@mail.gmail.com>
@ 2023-04-19  8:18       ` Michael Olbrich
       [not found]         ` <CABDcavb8Xsvxct4B+34KvNJJFLPn4bDfQ6OV_0ZQ8mkVCQTQ2A@mail.gmail.com>
  0 siblings, 1 reply; 3+ messages in thread
From: Michael Olbrich @ 2023-04-19  8:18 UTC (permalink / raw)
  To: Guillermo Rodriguez Garcia; +Cc: ptxdist

On Wed, Apr 19, 2023 at 09:28:02AM +0200, Guillermo Rodriguez Garcia wrote:
> El miércoles, 19 de abril de 2023, Michael Olbrich <m.olbrich@pengutronix.de>
> 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.rodriguez@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-5555 |



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [ptxdist] Regenerate license report
       [not found]         ` <CABDcavb8Xsvxct4B+34KvNJJFLPn4bDfQ6OV_0ZQ8mkVCQTQ2A@mail.gmail.com>
@ 2023-04-21  5:29           ` Michael Olbrich
  0 siblings, 0 replies; 3+ messages in thread
From: Michael Olbrich @ 2023-04-21  5:29 UTC (permalink / raw)
  To: Guillermo Rodriguez Garcia; +Cc: ptxdist

On Thu, Apr 20, 2023 at 12:24:21PM +0200, Guillermo Rodriguez Garcia wrote:
> El mié, 19 abr 2023 a las 10:18, Michael Olbrich (<m.olbrich@pengutronix.de>)
> escribió:
> > On Wed, Apr 19, 2023 at 09:28:02AM +0200, Guillermo Rodriguez Garcia wrote:
> > > El miércoles, 19 de abril de 2023, Michael Olbrich <
> > m.olbrich@pengutronix.de>
> > > 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.rodriguez@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.
> >
> 
> Yes; the problem is that I was not actually changing the .make files.
> Instead I have a rules/post/licenses.make file where I override some of the
> xxx_LICENSE variables. I was looking for a way to regenerate the report
> when this file was updated. Anyway I think all is clear now with your
> explanations. Thanks again!

Which PTXdist version? Since PTXdist 2021.12.0 you can use
rules/<pkg>.<something>.make for that. These files are included directly
after rules/<pkg>.make and they are part of the hash that determines if a
package needs to be rebuilt.

Regards,
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-5555 |



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-04-21  5:29 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CABDcavZ=rUvonAmSRf9vwwxnPeHk3R_1gDopvqX-dbTgOxZc9w@mail.gmail.com>
     [not found] ` <CABDcavbWjKNGU83TJrGJf1SroL_dThjGw0utU=vhvw6+t3x8=w@mail.gmail.com>
2023-04-19  7:23   ` [ptxdist] Regenerate license report Michael Olbrich
     [not found]     ` <CABDcavach4LT-_LcLvnGY5tzr0ungz0pAnNbSLJgwFf-xS1MPw@mail.gmail.com>
2023-04-19  8:18       ` Michael Olbrich
     [not found]         ` <CABDcavb8Xsvxct4B+34KvNJJFLPn4bDfQ6OV_0ZQ8mkVCQTQ2A@mail.gmail.com>
2023-04-21  5:29           ` Michael Olbrich

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox