On Sun, 2006-01-08 at 13:59 -0500, Steve M. Robbins wrote: > It builds OK, though there are a number of lintian warnings of > the nature: > > W: libinsighttoolkit4-dev: executable-not-elf-or-script > ./usr/include/InsightToolkit/Algorithms/itkBayesianClassifierImageFilter.txx > > Those should be easily fixed.
Yes, I've fixed all the permission warnings, and I'll send a script upstream to fix this there too. Also changed is the standards-version, fixed up a build-depends on cmake, and a few other minor things. Andreas picked up a problem: W: libinsighttoolkit4: package-name-doesnt-match-sonames ... which is because there are multiple (like about 25) libraries that comprise the base system. So this isn't really fixable, as the only solution would be to split each .so into its own package, which makes no sense. So I guess we just ignore this warning. > I'm keen to have ITK uploaded to debian. I notice that the ITP bug > (#184554) was closed when the packages were uploaded to > mentors.debian.net. That's not really what's intended; rather, the > bug should remain open until the packages are uploaded to debian > proper. Mea culpa, still learning. Should I reopen it until it ends up in main or just leave it? > I guess we also need CableSwig uploaded to Debian. Yes, I've been working on it and CableSwig 2.4 is now packaged, and availabe at: http://mentors.debian.net/debian/pool/main/c/cableswig/ > I couldn't find any ITP or RFP for it. There's one now! :) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=348156 > Have you had a chance to produce packages with bindings? Yes, I've got a first cut. It now builds using the new CableSwig package and includes bindings, which I have briefly tested and works great. (BTW, it takes a good 5 hours or so, and takes several gig of space!) The problem now is getting the Python and Tcl files to install in the appropriate places as per policy. At the moment they mostly get installed into /usr/lib/InsightToolkit. AFAICT all the .py files should go into: /usr/lib/pythonX.X/site-packages/InsightToolkit But the Python policy doesn't seem to specify where the shared libraries go. I guess they belong in /usr/lib with the rest of them. So now that the default installation works, I just need to change the CMakeList.txt scripts to put things in the right place as above. :: Gavin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
