[COOT] Coot versions [was Re: Coot web page is down]
On 30/09/10 15:06, Leon Flaks wrote: Now as web page is back on-line ( Thanks! ) Thanks to Richard Bryan (it was an NFS issue). I have a question about the source, which I could not find on the mirror. I am trying to build the latest 0.6.2-pre1 on fedora 13 64-bit, with the goal of building rpm out of it. I have rpm of the latest stable version, but it is a bit out of date, the spec file in it is a very good starting point. I can see two places to grab the source - one at http://www.biop.ox.ac.uk/coot/software/source/pre-releases/ and another at http://coot.googlecode.com/svn/trunk/ The same revision number has huge differences - untared directories are 76M and 173M - that is release 3191. Even the doc directory is different. OK, were are in a bit of an unusual situation at the moment (normally, trunk is the latest pre-release, but not right now). http://www.biop.ox.ac.uk/coot/software/source/pre-releases/ contains the 0.6.2 pre-release tar files http://coot.googlecode.com/svn/trunk/ contains 0.7 pre-release. I was (am) working on this while we fix up the final bugs and compilation issues for 0.6.2 (primarily because Bernhard went on holiday and there was a Window/Clipper issue to fix and I didn't want to add experimental/new code to 0.6.2). I discussed this in my blog http://lmb.bioch.ox.ac.uk/emsley-blog/ Paul.
Re: [COOT] Coot versions
Victor Alves schrieb: Hello Since Ubuntu 9.04 now comes with Python 2.6, is there among the various Coot versions available in Nightly builds, one that comes with GTK2 but not with Python? I hope this is not a very dumb question, but in my ignorance I have these all kind of mixed up, namely which of the various Coot versions available come with GTK1, GTK2, Guile, Python. Any other variations? there is a very simple solution: stop adding things to your $PATH. Instead, use a wrapper script that sets the PATH and other req'd environment variables for the program you want to run. E.g. have the following /usr/local/bin/coot : #!/bin/csh -f setenv PATH /where/ever/coot/was/installed/bin:$PATH setenv COOT_BACKUP_DIR /tmp exec coot $* or some such (I am typing from memory) - you get the idea (you don't have to use csh). In this way you may install as many python versions as your disk can accommodate. One other question. In this link, http://www.ysbl.york.ac.uk/~emsley/coot/build-info Should I not use any builds which are red? What about the size of the green bar? from quick inspection I would guess that green bars mean built less than 24 hours ago and red bar more than 1 day old. Thanks in advance Victor Alves smime.p7s Description: S/MIME Cryptographic Signature
Re: [COOT] Coot versions
Hi Victor, typing from memory is always problematic (in my case at least). My little C wrapper would not work because exec coot $* relies on the $PATH setting, and if that has /usr/local/bin it would call itself recursively. For the record, this is the (actual) /usr/local/bin/coot that we use: #!/bin/csh -f setenv LANG C exec /usr/local/src/coot-Linux-x86_64-centos-5-gtk2/bin/coot $* BTW the LANG setting solves a problem with the comma (,) versus point (.) interpretation of PDB files (a FAQ). Another BTW: the wrapper technique works nicely for phenix, cns, arpWarp, ... too, and would enable you to use different CCP4 versions in parallel, and so on - you get the idea. HTH, Kay Kay Diederichs schrieb: Victor Alves schrieb: Hello Since Ubuntu 9.04 now comes with Python 2.6, is there among the various Coot versions available in Nightly builds, one that comes with GTK2 but not with Python? I hope this is not a very dumb question, but in my ignorance I have these all kind of mixed up, namely which of the various Coot versions available come with GTK1, GTK2, Guile, Python. Any other variations? there is a very simple solution: stop adding things to your $PATH. Instead, use a wrapper script that sets the PATH and other req'd environment variables for the program you want to run. E.g. have the following /usr/local/bin/coot : #!/bin/csh -f setenv PATH /where/ever/coot/was/installed/bin:$PATH setenv COOT_BACKUP_DIR /tmp exec coot $* or some such (I am typing from memory) - you get the idea (you don't have to use csh). In this way you may install as many python versions as your disk can accommodate. One other question. In this link, http://www.ysbl.york.ac.uk/~emsley/coot/build-info Should I not use any builds which are red? What about the size of the green bar? from quick inspection I would guess that green bars mean built less than 24 hours ago and red bar more than 1 day old. Thanks in advance Victor Alves smime.p7s Description: S/MIME Cryptographic Signature
Re: [COOT] Coot versions
Kay Diederichs wrote: Victor Alves schrieb: One other question. In this link, http://www.ysbl.york.ac.uk/~emsley/coot/build-info Should I not use any builds which are red? What about the size of the green bar? from quick inspection I would guess that green bars mean built less than 24 hours ago and red bar more than 1 day old. That's right. Because the builds happen every night [1] the colours are a hint to us that something may have gone wrong in the daily/nightly builds. I have been thinking about reworking this page, because now that it is used by users (not just developers) it is problematic that a big red bar sometimes represents a quite recent build (as the comment from Victor suggests). Paul. [1] actually, there are exceptions, which make things non-straightforward.
[COOT] Coot versions
Hello Since Ubuntu 9.04 now comes with Python 2.6, is there among the various Coot versions available in Nightly builds, one that comes with GTK2 but not with Python? I hope this is not a very dumb question, but in my ignorance I have these all kind of mixed up, namely which of the various Coot versions available come with GTK1, GTK2, Guile, Python. Any other variations? One other question. In this link, http://www.ysbl.york.ac.uk/~emsley/coot/build-info Should I not use any builds which are red? What about the size of the green bar? Thanks in advance Victor Alves
