[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFC: casacore-2.1.0-1 debian package

Benda Xu <heroxbd@gentoo.org> writes:
> Gijs Molenaar <gijsmolenaar@gmail.com> writes:
>>    Do you mean "libcasa-mirlib2" and friends? Are you suggesting they
>>    should be named "libcasacore-mirlib2", or "casacore-mirlib2"?
>> yes. Don't use the name casa.
> Why does the upstream name its shared libraries libcasa_meas.so, etc.?

The package name should just follow the library name here, and unless
there is a good reason to deviate from the name given by upstream, I
would stay with their name.

Especially for shared libraries, this is not a big problem: they are
usually not installed by hand, but by dependencies. So, the end user
will probably never see them, and so there is no cause for confusion.

>> ok sure . There is no public method for reporting bugs and having
>> discussions?
> This mailing list is public.  Issues can be grouped into threads.

I would strongly support this; this is was the mailing list is for.
Another location would be the ITP bug report for the package.
Once the package is in Debian (hopefully soon), we can make use of the
Debian bug system.

>>     I am not sure. Python3 builds alright and is put into
>>     "libsasa-python2" along with python2 bindings. "2" in the package
>>     name means casacore soname 2, a bit misleading to include python3.
>> Shouldn't we split those in true debian fashion? 
> The scheme I am using is practised by boost-python:
> $ dpkg -L libboost-python1.58.0
> ...
> /usr/lib/x86_64-linux-gnu/libboost_python-py27.so.1.58.0
> /usr/lib/x86_64-linux-gnu/libboost_python-py34.so.1.58.0
> /usr/lib/x86_64-linux-gnu/libboost_python-py35.so.1.58.0
> python 2.7, 3.4 and 3.5 are packaged into a single Python binding
> package.

This is ugly, since then using the package for Python-2 would also pull
the Python-3 libraries as dependency and vice versa. Both libraries are
used in conjunction, and only rarely together, so it does not make sense
to combine them in one package.

Please put them into separate packages. For the package name of the
Python 3 package I am not sure; please ask on debian-mentors for an

BTW, something went wrong with the Python-3 library; it is still linked
against Python 2.7, and not Python3:

$ ldd libcasa_python3.so.2.1.0 
	linux-vdso.so.1 (0x00007ffc1dfd7000)
	libcasa_casa.so.2 => libcasa_casa.so.2 (0x00007f1beca08000)
	libboost_python-py35.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_python-py35.so.1.58.0 (0x00007f57d3b43000)
	libpython2.7.so.1.0 => /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 (0x00007f57d35b5000)
	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f57d323a000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f57d3024000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f57d2c7f000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f57d2a7b000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f57d285e000)
	libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007f57d265a000)
	librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f57d2452000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f57d2154000)
	libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f57d1f38000)
	/lib64/ld-linux-x86-64.so.2 (0x00005568169c4000)

Best regards


Reply to: