Note on a Fedora system download fys_fc.repo instead, and use fys_fc identifier in the command below.
Moreover on a fc system you do not need to include any external repositories.

Note on an openSUSE system download fys_openSUSE.repo instead and save it under /etc/zypp/repos.d, and use fys_openSUSE identifier in the command below.
You need to include additional external openSUSE repositories: see
configure external repositories

list all packages available in the fys yum repository, maybe you need some of them?:

Have a look at the /opt/campos-dacapo-2.7.16/share/campos-dacapo/*.*sh
to see what environment variables need to be set in case of an installation
into a non-default prefix. There is also a template modulefile
/opt/campos-dacapo-2.7.16/share/campos-dacapo/campos-dacapo-2.7.16*
that contains `prereq`ired modules (modulefiles surely are different on your system).

On systems where you don't have root access you can consider downloading RPMS individually and extracting
the contents of the RPMS, for example:

Note: do not install the RPMS generated in the last step on the login node. They need to be installed only on compute nodes.
On the login node only the module file needs to be deployed under ~rpmbuild/modulefiles, as rpmbuild.
Note that this directory is available as svn checkout at https://svn.fysik.dtu.dk/projects/modulefiles/trunk.
Here is what need to be done for a new version of the package:

Note: do not install the RPMS generated in the last step on the login node. They need to be installed only on compute nodes.
On the login node only the module file needs to be deployed under ~rpmbuild/modulefiles, as rpmbuild.
Note that this directory is available as svn checkout at https://svn.fysik.dtu.dk/projects/modulefiles/trunk.
Here is what need to be done for a new version of the package:

Note: do not install the resulting RPM on the login node. It needs to be installed only on compute nodes.
On the login node only the module file needs to be deployed under ~rpmbuild/modulefiles, as rpmbuild.
Note that this directory is available as svn checkout at https://svn.fysik.dtu.dk/projects/modulefiles/trunk.
Here is what need to be done for a new version of the package:

Unfortunately, from 10.3 version mkl depends on intel libraries located in directories outside of mkl.
This causes troubles for numpy which requires (is there a way to fix that?) all non-standard libraries to be located in one directory.
Therefore one may need to create a link (currently not performed):

NetCDF (network Common Data Form) is an interface for array-oriented
data access and a library that provides an implementation of the interface. The NetCDF library also defines a
machine-independent format for representing scientific data.

We prefer version 3.6.1
or higher (note that version 3.6.2 has fortran interface in libnetcdff.a).

If you build only a serial version add "--without parallel" to the rpmbuild options.
Another useful option is "--without default_version" that does not put /etc/profile.d scripts,
nor modules under /opt/modulefiles that allows the package to be relocatable.

Warning: currently (9 Oct 2008) packaging of openmpi on FC8/FC9 requires the following link to be made:

siesta (Spanish Initiative for Electronic Simulations with Thousands of Atoms)
is both a method and its computer program implementation, to perform electronic structure calculations and ab initio molecular dynamics simulations of molecules and solids.

yambo is a FORTRAN/C code for Many-Body calculations in solid state and molecular physics.
Yambo relies on the Kohn-Sham wavefunctions generated by two DFT public codes: abinit, and PWscf.
This build creates interfaces to abinit and PWscf.

Program Database Toolkit is a framework for analyzing source code written in several programming languages
and for making rich program knowledge accessible to developers of static and dynamic analysis tools. PDT is required by TAU.

Installed with restricted access under vasp UNIX group (needs te be created in advance).

vasp potentials

Download potpaw/potcar.date.tar, potpaw_GGA/potcar.date.tar, and potpaw_PBE/potcar.date.tar
to ~/rpmbuild/SOURCES. Create links to the downloaded files so the files
are named explicitly with the string date (not the actual dates), for example: