Re: Packaging Barcode Writer in Pure PostScript
Hi,
I've removed the Makefile and made use of dh_install. I've also
slimmed the debian/rules file by removing the commented lines and dh_*
rules that seem redundant, as suggested. I would appreciate it if
someone could offer any assistance in further tidying this up.
It is now also building for Architecture: all, but linda gives be the
following message:
W: libpostscriptbarcode; File /usr/lib/libpostscriptbarcode/barcode.ps
contained in /usr/lib of Architecture: all package.
Instructions and example uses for using the library are given on the
project homepage at http://www.terryburton.co.uk/barcodewriter as
stated in the README file.
Please could people review the changes that I've now made. Files are
at http://www.terryburton.co.uk/barcodewriter/files/debiansrc.
Many thanks,
Tez
On 06/09/05, Marc 'HE' Brockschmidt <he@debian.org> wrote:
> Terry Burton <tez@terryburton.co.uk> writes:
> > Would people please examine the package and tell me what problems
> > exist. You can view the files at
> > http://www.terryburton.co.uk/barcodewriter/files/debiansrc
>
> The debian/rules is very bloated, please remove everything which is not
> needed and not mandated by Policy (the CFLAGS bits, for example)
>
> > The project has no dependancies. Is it safe to remove this line from
> > the control file?
> > Depends: ${shlibs:Depends}, ${misc:Depends}
>
> What do you need to use this PostScript thingy? There is no Debian
> package without a Depends line, as you always need something else to
> properly use it.
>
> > The upstream project unpacks all files into a single directory and
> > does not provide a facility for installing the files into a distro's
> > file system hierarchy. For the Debian package I have created a
> > Makefile that accomplishes his via the install target.
>
> You don't need that, you can use dh_install in debian/rules.
>
> > Debian Policy mandates that programs have a manpage. Since this is a
> > PostScript resource (similar to a shared library) does this rule still
> > apply. If so then I'm not sure what the content of such a manpage
> > ought to be.
>
> There should be some documentation, not necessarily as man page.
>
> > The project is platform independant as specified in the control file.
>
> No, you didn't. Please look up the difference between Arch: any and
> Arch: all.
>
> Marc
> --
> BOFH #348:
> We're on Token Ring, and it looks like the token got loose.
>
>
>
Reply to: