tar is used to archive several files into one.
A compression method is then often applied to that file.
And that is what you have., a compressed archive of several files. Those several files can be anything. Though I admit that (specialy in the Linux world) they often contain the files that are needed (and sufficient) to build a product on a system. And then a certain amount of standardisation is often used to gather information about the system (the configure part), to build the product (the make part) and to install the product (the make install part, that should be run as root). Also, it is often the case that a file READ.ME (or similar named) file is added to such a “tarball” to explain how to build and install.
This seems not to be the case in the archive you have. We can only guess what should be done with this (you seem to think that it contains some software product). Questions arise like:
. where did you find this?
. is there any story there which told you what to expect?
. any docs there on how to install/run it?
Extract the whole contents of the archive file to a directory. Then, execute VESTA in that
directory by double-clicking the \VESTA" file on a file manager or by typing the following
command in a command line:
Anyway, i installed some glut packages. There were no GLUI packages. I installed some other glu packeges, now it works.
Yet there is another small ishue: when starting the program, the following message appears:
(VESTA:18487): Gtk-WARNING **: Unable to locate theme engine in module_path: "oxygen-gtk",
it sounds like a missing gnome theme, do you have gnome installed?
it’s no big deal there are 2 packages that provide that and from what I’ve read they should be compatible just zypper them
zypper in oxygen-gtk3
strangely enough I could find binary packages for oxygen-gtk3 (or oxygen-gtk2) only source.
on the other hand the binary uses old gtk2 library it might be better to install the gtk2 widget
only when:
a) it is in a directory mentioned in your PATH environment varianle (that is why you are advised to put it in the bin directory in your home directory ~/bin);
b) it is made executable for the user that wants to execute it, thus when you are the owner and you did the chmod as mentioned above, that is OK.
Because in your case, the executable file VESTA is somewhere else, people here advised you the “wrapper”. Alternative solution (there are always many solutions in Unix/Linux) would be to add the directory where VESTA resides to your PATH. To achieve this you could add to your ~/.bashrc:
PATH=$PATH:/home/carborane/VESTA-x86_64
(replace carborane with your real username).
I would prefer the wrapper, were it only for the fact that calling a program with uppercase characters is very un-Unix/Linux like >:)
> Because in your case, the executable file VESTA is somewhere else,
> people here advised you the “wrapper”. Alternative solution (there are
> always many solutions in Unix/Linux) would be to add the directory where
> VESTA resides to your PATH.
Or add an alias, on file ~/.alias:
alias vesta="/home/carborane/VESTA-x86_64/VESTA"
An alias file can make adaptations to several programs in a single file.
Each script in ~/bin uses a minimum of 8 KB, and that’s a waste
(kidding)
(I can reverse the argument, though, against use of aliases in terms of
resources)
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)