Thanks for the heads up, Vincent ! On 03/11/2011 22:32, Vincent Fourmond wrote: > > This leads me to the bad news: jalview is fresh but already broken. > Debian now ships jmol version 12.2.2 (that's the stable release, isn't > it ?), and jalview doesn't build against it. > > Although I could tackle porting to the newer jmol, I guess it won't > take much time to you. I'm attaching the build failure log in case > someone wants to have a look. If no one steps forward, I'll give it a > try ;-)... I've been watching the jmol-dev list with feelings both of fear and wonderment - they have just completed a major refactoring in order to support an android build, and I've been looking at the new architecture to see how jalview might be refactored to achieve the same goals. I think some of the changes were already pushed into the 12.2 stream.
I'll take a look at this over the next few days and see if it can be rectified. If it can, I'll push changes to both the 2.7, master and develop branch. Unfortunately, I was somewhat concerned that this might happen with the packaging. Unless there is an explicit API jar generated by a project, they are almost always likely to change their APIs at every release. Would it be possible to specify a specific Jmol.deb that Jalview.deb requires ? As I understand it, the FTPmasters preserve all older versions. I suppose the alternative would be to have a 'jalview-jmol.deb' which provides the latest compatible Jmol - either as a virtual package or as a snapshot. Jim. _______________________________________________ Jalview-dev mailing list [email protected] http://www.compbio.dundee.ac.uk/mailman/listinfo/jalview-dev
