We did something similar, some time ago.
We have used make dependencies to generate csv along with pdf report.
I have sent the patch to list.
Regards Denis
Am Mittwoch, den 28.03.2018, 22:31 +0200 schrieb Andreas Pretzsch:
> On Di, 2018-03-27 at 09:26 +, Alm, Michael wrote:
> >
> > Also, it
On Di, 2018-03-27 at 09:26 +, Alm, Michael wrote:
> Also, it would be helpful to have a short-list with the package name, version
> and license
> type only, without all the license text. Maybe like this:
>
> 'ptxdist license-report target short'
>
> foo, 1.0, BSD
> bar, 2.8.1.5, GPLv2
>
Hi,
On Tue, Mar 27, 2018 at 09:43:35AM +0200, Michael Olbrich wrote:
> > > Is it possible to generate such a report? How?
> >
> > This should probably be documented. You can get it via
> >
> >$ ptxdist make license-report
>
> That's currently the way to do this. It's not documented because
Hello,
On Tue, Mar 27, 2018 at 09:43:35AM +0200, Michael Olbrich wrote:
> I want to move this stuff out of rules/post/ and do something similar to
> the image rules. And then hook up these new packages these packages
> somewhere. I'm not sure 'world' is the correct place, so a new command
>
Hi,
On Mon, Mar 26, 2018 at 09:44:17AM +0200, Roland Hieber wrote:
> On 22.03.2018 10:51, Alexander Dahl wrote:
> > from the Git repository and some hints in the ptxdist source code I assume
> > ptxdist can generate some kind of license report, based on the FOO_LICENSE
> > variables in each
On 22.03.2018 10:51, Alexander Dahl wrote:
Hello,
from the Git repository and some hints in the ptxdist source code I assume
ptxdist can generate some kind of license report, based on the FOO_LICENSE
variables in each packages make rule. However I could not find any hint on how
to generate this
Hello,
from the Git repository and some hints in the ptxdist source code I assume
ptxdist can generate some kind of license report, based on the FOO_LICENSE
variables in each packages make rule. However I could not find any hint on how
to generate this report in:
* documentation (ptxdist
