hi all,
i am working on a project for packaging a python script , and perhaps that we
can cooperate if you want,the problem that i did face and i was trying to get
away of is the use of automake and autoconf in the procedure of the
Maintainer's Guide which is supposed to give the Makefile eventually when you
the command configure.
i did do apt-get source x for one of the perl packages and i went inside the
directories and i modified its contents for another perl script and i was able
to develop the debian package according to the procedure.
if you can get the source of a python script by the same methodology i think
that it should work, i will be waiting for your reply for that.
Regards,
Amr
Matthias Klose ([EMAIL PROTECTED]) wrote:
>
> Bruno Dusausoy writes:
> > Hi,
> >
> > I'd like to package the python bindings of TagLib (1.2 first, 1.3 when
> > it will be released in Debian). This is my first attempt to make a
> > debian package.
> >
> > It's pretty tiny (only 3 .i files, 1 .cxx file, the Makefile and the
> > resultings files : TagLib.py and _TagLib.so).
> >
> > I've read both "Debian New Maintainer's Guide" and "Debian Python
> > Policy" documents, but couldn't find an answer to this question : when i
> > do the initial "debianization", what do I chose when dh_make asks me the
> > kind of package I want to do (single binary, multiple binary, library,
> > or kernel module?).
> > Is this a library or a single binary ?
>
> If you want to provide the package for one python version only, then
> you need the single binary. For supporting more than one python
> version, maybe look at a similiar package (i.e. pygresql). The
> multiple binary template only adds a -doc package, so it doesn't help
> much.
>
> Matthias
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>
