mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC 0/2] add a way to extract license text from packages
Date: Thu, 19 Feb 2015 15:12:03 +0100	[thread overview]
Message-ID: <20150219141203.GM30223@pengutronix.de> (raw)
In-Reply-To: <54E2F761.9070605@tqsc.de>

On Tue, Feb 17, 2015 at 09:10:09AM +0100, Markus Niebel wrote:
> Am 11.02.2015 um 14:02 schrieb Michael Olbrich:
> > On Wed, Feb 11, 2015 at 12:19:34PM +0100, Juergen Borleis wrote:
> >> On Wednesday 11 February 2015 11:50:16 Hubert Feurstein wrote:
> >>> IMHO the proposal by Markus makes sense. I have had the same issues
> >>> with collecting license texts in the past. So a solution integrated in
> >>> PTXdist would be great. Because then it would be possible to collect
> >>> the license texts depending on the config options of a package
> >>> (sometimes plugins have a different license).
> >>
> >> Please checkout current PTXdist master and run "ptxdist make license-report" 
> >> inside a PTXdist project. You need "LATEX" and "dot" to make it work.
> > 
> > xelatex (from texlive-xetex in Debian) and dot2tex are needed as well.
> > 
> 
> Thank you, test looks promising and generated data are very helpfull. 
> Just a hint for documentation - recent versions of the LATEX packages are needed, 
> because of style packages used.

It worked on my Debian unstable :-). I'd be happy to take patches that make
it work with older versions if there is a need for that.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2015-02-19 14:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21  8:12 Markus Niebel
2015-01-21  8:12 ` [ptxdist] [RFC 1/2] ptxdist: add license text extraction Markus Niebel
2015-01-21  8:12 ` [ptxdist] [RFC 2/2] icu: add LICENSE_TEXT Markus Niebel
2015-01-29  7:45 ` [ptxdist] [RFC 0/2] add a way to extract license text from packages Markus Niebel
2015-01-29 20:23   ` Guillermo Rodriguez Garcia
2015-01-30  7:48     ` Markus Niebel
2015-02-10 13:14       ` Guillermo Rodriguez Garcia
2015-02-11 10:50       ` Hubert Feurstein
2015-02-11 11:19         ` Juergen Borleis
2015-02-11 13:02           ` Michael Olbrich
2015-02-17  8:10             ` Markus Niebel
2015-02-19 14:12               ` Michael Olbrich [this message]
2015-02-12  7:33           ` Markus Niebel
2015-02-12  8:55             ` Robert Schwebel
2016-10-03 22:23           ` [ptxdist] license-report: extend to generate textual list of package + licenses Andreas Pretzsch
2016-10-04 13:02             ` Michael Olbrich
2016-10-04 17:15               ` Andreas Pretzsch
2016-10-05 12:53                 ` Michael Olbrich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150219141203.GM30223@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox