Re: Status of InVesalius packaging (Was: Status of SIGAR (Was: InVesalius packaging))
On Thu, Mar 17, 2011 at 7:36 AM, Andreas Tille <andreas@an3as.eu> wrote:
> Hi,
Hi Andreas,
> I just wanted to give a ping about the status of InVesalius. It seems
> that sigar did not made some progress (at least I can not find it in
> Debian). Can you please give an update whether some help is needed or
> what issues are open?
I was in touch with Michael Hanke some months ago about sigar
packaging. Acording to him, these were the problems:
- build dependency 'ant' seems to be missing
- changelog doesn't list ITP bug number
- in debian/control libsigar package has section 'lib' but should be
'libs' or removed
- there are lots of *.ex files in the dsc (but not in git)
- any reason to use --with-quilt in debian/rules explicitely? If yes,
then quilt build-dep is missing
- I saw that you build a shared lib of libsigar -- did you talk to
upstream about SO version management yet?
- debian.copyright is still a template
- a debclean doesn't clean things properly
I was trying to package the java binding but I wasn't able, so I
thought to not package the java binding. But the other problems I
haven't seen yet. Michael Hanke created a branch in github to do the
sigar packaging (https://github.com/hanke/sigar/tree/debian) and I
forked that (https://github.com/tfmoraes/sigar/tree/debian), but I
didn't have time to work in it.
> Kind regards
>
> Andreas.
Thanks!
Thiago Franco de Moraes.
> On Mon, Mar 29, 2010 at 03:27:55PM -0400, Michael Hanke wrote:
>> Hey,
>>
>> On Mon, Mar 29, 2010 at 03:46:20PM -0300, Thiago Franco Moraes wrote:
>> > On Mon, Mar 29, 2010 at 10:40 AM, Andreas Tille <andreas@fam-tille.de>wrote:
>> > W: libsigar: package-installs-python-pyc
>> > usr/lib/python2.6/dist-packages/sigar.pyc
>> > N:
>> > N: Compiled python source files should not be included in the package.
>> > N: These files should be removed from the package and created at package
>> > N: installation time in the postinst.
>> > N:
>> > N: Severity: normal, Certainty: certain
>> >
>> > How can I only compile in installation time? I'm using this command in rule
>> > file to install the files:
>> >
>> > cd $(CURDIR)/bindings/python && python setup.py install --install-layout=deb
>> > --root=$(CURDIR)/debian/$(PACKAGE)
>>
>> I wasn't following this effort before -- forgive me if that had been
>> talked about before.
>>
>> Looks like the Python-bindings (and others too) should go into separate
>> binary packages and be handled by proper tools. pysupport should take
>> care of all Python-related issue (including the one above).
>>
>> Is there any reason for this verbose rules file. Both debhelper7 and
>> cdbs should help a lot with the common cases of packaging (like this
>> one) and also provide convenient helpers for python packages.
>>
>> I might be able to help with the general and python-related aspects of
>> this packaging, but wanted to ask first if there is need to stay close
>> to the current state?
>>
>> Right now the packaging looks quite raw -- lots of unused/unedited
>> files. The rules file only seems to build the python-bindings and none
>> of the rest -- including the main library -- is that intended?
>>
>> Given these facts the binary package should be named 'python-sigar'.
>>
>> Is there a repository for this packaging somewhere? You chose to take an
>> SVN snapshot (upstream also offers the code in git). Did you just
>> download that snapshot or have the code in a repository together with
>> the packaging?
>>
>> Michael
>>
>>
>> --
>> GPG key: 1024D/3144BE0F Michael Hanke
>> http://mih.voxindeserto.de
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-med-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>> Archive: http://lists.debian.org/20100329192755.GA22928@meiner
>>
>>
>
> --
> http://fam-tille.de
>
>
Reply to: