Re: Packaging Barcode Writer in Pure PostScript
Hi,
Thanks for all of your assistance Eric.
New files available at
http://www.terryburton.co.uk/barcodewriter/files/debiansrc.
Documentation files moved from debian/install to debian/docs.
Depends removed.
I would prefer not to have to regenerate the documentation from TeX
for the timebeing since it relies on TeX modules that are not yet part
of Debian. Hopefully future Debian releases of the PSTricks packages
will remedy this situation making this a sensible option. It would
also seem a bit overkill to have such a simple library depend on
something as large as LaTeX.
Many thanks,
Tez
PS: I don't think I'll bother with another name change. I've just
filed an ITP report for the project as libpostscriptbarcode against an
existing RFP for postscriptbarcode. I'm sure that will ruffle a few
DDs feathers, but changing project name again may make some of them
fall off their perch! No offence intended... :-)
On 06/09/05, Eric Lavarde - Debian <deb@zorglub.s.bawue.de> wrote:
> Hi,
>
> sorry for this, but I think another round might be required:
> 1. move sample.ps, barcode_with_sample.ps, docs/* from debian/install to
> debian/docs.
> 2. I think you should just remove the Depends line (as far as I understand
> the thing you could just "cat barcode_with_sample.ps > /dev/lp0" and it
> would bring something to the user).
> 3. the documentation under docs/* is always the same in different formats,
> I understand that the correct way to do this would be to package only the
> source of this documentation (TeX or whatever) and generate the different
> formats on-the-fly during packaging.
> (but someone else might want to confirm on this last one before you take
> the hassle of doing this).
>
> Cheers, Eric
>
> PS: more as a joke you could rename your package to libbarcodewriter-ps in
> order to align the name with libwhatever-perl or libwhatever-java :->
>
> --
> Eric de France, d'Allemagne et de Navarre
>
Reply to: