Dear David and Debian-Med, I just skimmed through your conversation on the packaging of Odin and I am happy to see the progress. To avoid potential problems as soon as possible, I have the following little comments and questions:
- I admit that I have been quiet lazy when it comes to sonames of the libraries. Since the binary interface changes frequently (even for each minor release), I just tried to used the version number of Odin. I know this is wrong... Any suggestions are welcome ;-) - The sequence examples/templates, the samples and the coil files are an important component. Although, technically, Odin can be executed without them, this would be an unrealistic scenario. Thus, I would suggest to bundle them as closely to the Odin GUI as possible. - When splitting up Odin into several packages, would it be possible to have a (empty) meta-package 'odin' with proper dependencies to install all sub-packages? - The binary 'odintestsuite' is just a unit test of several core components and could be removed from the final package, if size is an issue. - There are several (hidden) dependencies of Odin. For instance, the GUI assumes a working 'g++' to compile and link the sequences on the fly, or 'gdb' and 'xterm' to debug sequences. Would it be possible to include these in the dependency list? Best wishes, Thies (Odin upstream) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
