Re: MIA - Software for medical image alaysis
Hello,
thanks for the pointers. I made myself an Alioth account (gert-guest)
and will star to move the packages from ubuntus bazaar to the git structure.
----
First some additional status:
vistaio:
* Licencing: is distributed under a BSD style license (the original
license).
* Code: I did a release that changes all the function and structure
names to avoid a possible name conflict with what is distributed in the
libvia package.
everything else:
* Licencing: All GPL2+ or GPL3+, all contributions were made by me or
under my supervision, so I made sure the license is correct.
-----
Now for some questions:
- should I make an ITP bug for each package, or is it better to group
the ITPs for packages that are closely related. i.e.
vistaio - required for all other packages
mia + pymia + viewitgui (mia is required by the other two)
mialm + mialmpick - (mialm is requiered by mialmpick)
- anybody has used the git-bzr-ng tool to bridge between bazaar (Ubuntu
packaging repro) and git (debian-med)?
https://github.com/termie/git-bzr-ng the thing is it hasent seen a
stable release yet.
- lintian:
My libmia package contains more than one shared library, so I guess I
should override the "package-name-doesnt-match-sonames", right?
The libmia-doc created by Doxygen contains a "jquery.js"
(embedded-javascript-library). I read that one should add the according
package as dependency and remove the javascript, tried it, but is seems
that the system provided jquery.js is different, i.e. the documentation
web page didn't work properly. So I'd override this as well.
mia-viewitgui and mialmpick:
binary-without-manpage - what kind of man page is common for GUI
programs (apart from possible command line options)?
IMHO a man page should be helpful, but a GUI program will probably fare
better with a graphical tutorial, especially since specifying comand
line options is not really needed.
Many thanks,
Gert
Reply to: