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:HelloSince 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 withPython? 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
