Chimera 1.2540 installer options and unattended installation
Hi chimera-users, the Chimera installer seems to know some options and modifiers, but I could not find out what they mean: # ./chimera-1.2540-linux.exe -help UnZipSFX 5.41 of 16 April 2000, by Info-ZIP (Zip-Bugs@lists.wku.edu). Valid options are -tfupcz and -d <exdir>; modifiers are -abjnoqCLMVX. # Does anybody know what these options and modifiers do or where I can read about them? My motivation is, that I'd like to install Chimera in a non-interactive way (batchscript) in a non-standard location. Is there a way to achieve that? Thanks in advance frank -- Frank Thommen - Structures IT Management and Support - EMBL Heidelberg structures-support@embl-heidelberg.de - +49 6221 387 8353
Frank Thommen wrote:
the Chimera installer seems to know some options and modifiers, but I could not find out what they mean:
# ./chimera-1.2540-linux.exe -help UnZipSFX 5.41 of 16 April 2000, by Info-ZIP (Zip-Bugs@lists.wku.edu). Valid options are -tfupcz and -d <exdir>; modifiers are -abjnoqCLMVX. #
Does anybody know what these options and modifiers do or where I can read about them?
My motivation is, that I'd like to install Chimera in a non-interactive way (batchscript) in a non-standard location. Is there a way to achieve that?
In my RPM specfile (which is essentially a non-interactive installation in a non-standard location) I use the following: %build instdir=${RPM_BUILD_ROOT}/opt/%{name}-%{version}-%{release} chmod u+x %{SOURCE0} %{SOURCE1} %ifarch x86_64 echo $instdir | %{SOURCE1} %else echo $instdir | %{SOURCE0} %endif i.e. I install in /opt/chimera-1.2540-1/ under my build root. SOURCE0 and SOURCE1 are the i386 and x86_64 packages straight off the website. I don't use any "interesting" flags though. Ben -- ben@salilab.org http://salilab.org/~ben/ "It is a capital mistake to theorize before one has data." - Sir Arthur Conan Doyle
On Mon, 4 Aug 2008, Frank Thommen wrote:
Hi chimera-users,
the Chimera installer seems to know some options and modifiers, but I could not find out what they mean:
# ./chimera-1.2540-linux.exe -help UnZipSFX 5.41 of 16 April 2000, by Info-ZIP (Zip-Bugs@lists.wku.edu). Valid options are -tfupcz and -d <exdir>; modifiers are -abjnoqCLMVX. #
Does anybody know what these options and modifiers do or where I can read about them?
My motivation is, that I'd like to install Chimera in a non-interactive way (batchscript) in a non-standard location. Is there a way to achieve that?
Thanks in advance
frank
On Linux, the chimera installer is a self-extracting zip file, so the options you see are the options unzipsfx accepts -- do "man unzipsfx" for more details. For batch installing, you'll need to give the installer an answer to the one question it asks by redirecting standard input to be from a pipe or a file. For example: chmod +x ./chimera-1.2540-linux.exe echo /usr/local/chimera | ./chimera-1.2540-linux.exe Good luck, Greg Couch UCSF Computer Graphics Lab
Hi Ben,
[...]
My motivation is, that I'd like to install Chimera in a non-interactive way (batchscript) in a non-standard location. Is there a way to achieve that?
In my RPM specfile (which is essentially a non-interactive installation in a non-standard location) I use the following:
[...]
Thanks. But for that solution I'd have to build an appropriate RPM first. That's probably too much effort for just one application as I'd have to learn how to do that first. Cheers frank -- Frank Thommen - Structures IT Management and Support - EMBL Heidelberg frank.thommen@embl-heidelberg.de - +49 6221 387 8353
Hi Greg,
[...]
My motivation is, that I'd like to install Chimera in a non-interactive way (batchscript) in a non-standard location. Is there a way to achieve that?
On Linux, the chimera installer is a self-extracting zip file, so the options you see are the options unzipsfx accepts -- do "man unzipsfx" for more details.
How silly of me. I should have noticed that from the '--help' output.
For batch installing, you'll need to give the installer an answer to the one question it asks by redirecting standard input to be from a pipe or a file. For example:
chmod +x ./chimera-1.2540-linux.exe echo /usr/local/chimera | ./chimera-1.2540-linux.exe
Great. That does the job perfectly. frank -- Frank Thommen - Structures IT Management and Support - EMBL Heidelberg frank.thommen@embl-heidelberg.de - +49 6221 387 8353
participants (4)
-
Ben Webb -
Frank Thommen -
Frank Thommen -
Greg Couch