***  For details on how to be removed from this list visit the  ***
***          CCP4 home page http://www.ccp4.ac.uk         ***


On Fri, 2006-04-21 at 18:54 -0700, Tim Fenn wrote:
> ***  For details on how to be removed from this list visit the  ***
> ***          CCP4 home page http://www.ccp4.ac.uk         ***
> 
> 
> After banging my head against the wall trying to get CCP4, SSM, MMDB
> and clipper installed in a multilib environment, I gave up and spent a
> few hours reconfiguring all the libraries to abide by GNU coding
> standards.  So, if you'd like, feel free to download:
> 
> ccp4c / ccp4f, mmdb, ssm and clipper from:

For the record, I have for a while been provided GNU autotooled versions
of mmdb, SSM, ccp4c and (old) clipper from 

http://www.ysbl.york.ac.uk/~emsley/software/ and extras therein


> clipper is only one library: libclipper.  I felt having a library for
> every filetype supported probably wouldn't scale well.  ;)

There is a finite number.

> I'd also like to try and get the packages accepted in the
> fedora-extras repositories, which is only one additional step beyond
> this point.  However, I'm afraid the CCP4 license may not allow for
> it, if I'm reading it correctly.  It seems the library is LGPL-ish,
> but only for academic users - is this true?  

If you get libccp4c from the above location, that is usable. (I have not
yet applied the patches from Ralf Grosse-Kunstleve).

> If so, Fedora won't let
> their repository system near it. Otherwise, I'd *gladly* continue
> depositing rpms to fedora-extras with other programs that depend on
> the above (coot, ccp4mg, etc.), so one day I could just run:
> 
> yum/smart install coot 

For my part, I'd be happy with that.

> on my stock fedora boxen, let yum/smart pull in all the dependencies
> and be done with it.  And given the build system, it would be a cinch
> to migrate everything to ubuntu, debian, RHEL, etc., and potentially
> save a few minutes of your system administrator's time.  ;)

The one main reason why I have not pushed this is because of conflicting
library names.  We haven't yet worked out a system to avoid that.

Paul.





Reply via email to