On Sun, Oct 14, 2012 at 4:33 PM, Thiago Franco de Moraes < totonixs...@gmail.com> wrote:
> Em 11-10-2012 03:36, Andreas Tille escreveu: > > Hi Thiago, >> >> On Wed, Oct 10, 2012 at 11:25:35PM -0300, Thiago Franco Moraes wrote: >> >>> I do not think that this was an explicite suggestion of Mathieu - he >>>> just intended to write what would be possible / acceptable packaging >>>> wise. It is definitely no good packaging practice to use convinience >>>> copies of some code which is developed somewhere else as in the source >>>> tree of the project in question. In Debian we try hard to modularise >>>> software and to not duplicate code. Just assume ca_smoothing could be >>>> used by some other imaging project. >>>> >>> >>> Ok. A question: Do you think it's better to split the package in >>> libcasmoothing and python-casmoothing or only python-casmoothing? >>> >> >> That's a bit tricky to answer for me because I have no idea about >> casmoothing at all. As a rule of thumb you should be guided by the >> answer to the question: Is there any chance that some libcasmoothing >> could be reasonably used without the Python interface or not? >> >> Kind regards >> >> Andreas. >> >> > > Hi Andreas, > > Sorry for the lack of feedback. I think I'll create only the > python-casmoothing. Before I start to package it I'll have to make some > modifications in cmake script I use to compile it. Modification related to > the installation of the python module generated in the compilation. > > Thanks! > I've just created the first package to ca_smoothing. The package name is python-casmoothing. dget -x http://dl.dropbox.com/u/817671/packages/packaging/python-casmoothing/python-casmoothing_0.1%7Egit357bbd1-1.dsc It takes so much time to package because I was busy converting our svn repository to git. Now, InVesalius code is hosted at https://github.com/invesalius/invesalius3. regards, Thiago.
