Hi,
Am Mittwoch, den 25.06.2008, 11:56 +0100 schrieb Penny Leach:
> As I see it, there are two options:
>
> 1. create two packages, one libbuffy-cli-perl which just contains the perl
> module and I can build pretty easily with dh-make-perl, and the other
> package containing the script itself, which depends on the first package
>
> 2. build one package and don't do the pm the normal way, but just install
> the script into /usr/bin, and the module into /usr/share/perl5/
>
> 1. seems like overkill but technically more correct and in line with policy?
> 2. seems much less complicated but potentially not correct?
I think when the .pm files are closely tight to the program, i.e., no
real public API and little use to other programs, then 2. is the correct
way, with, as Julian writes, /usr/share/${pkgname}/lib for the pm files.
If the library becomes more useful to others later, then this can still
be changed.
Greetings,
Joachim
--
Joachim "nomeata" Breitner
Debian Developer
nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil