SuSE Linux

Future (support planned) SuSE Linux releases:

• SuSE Linux 9.3 (i586)

  • Newest stable Midgard version: 1.7.6
  • Newest testing Midgard version: NA
  • Newest unstable Midgard version: NA

Old (support suspended) SuSE Linux releases:

• SuSE Linux 9.2 (i586)

  • Newest stable Midgard version: 1.7.6 (1.6.3 also available)
  • Newest testing Midgard version: NA
  • Newest unstable Midgard version: NA

• SuSE Linux 9.1 (i586)

  • Newest stable Midgard version: 1.6.2
  • Newest testing Midgard version: NA
  • Newest unstable Midgard version: NA

NOTE: Midgard is not working with selinux enabled (at least in Fedora this is confirmed)! If you know how to fix this issue (or if this is not affecting SuSE after all), please inform the Midgard developers on the Midgard IRC channel or send mail to the Midgard dev mailing list.

Install apt-libs and apt.

• For SuSE Linux 9.2:

from ftp://ftp.gwdg.de/pub/linux/suse/apt/SuSE/9.2-i386/RPMS.suser-rbos

• For SuSE Linux 9.1:

from ftp://ftp.gwdg.de/pub/linux/suse/apt/SuSE/9.1-i386/RPMS.suser-rbos

Import the GPG key.

• For SuSE Linux 9.2:

  mkdir /etc/apt/gpg
  cd /etc/apt/gpg
  wget -O MIDGARD-RPM-GPG-KEY http://www.puv.fi/download/midgard/suse/9.2/i586/RPM-GPG-KEY
  rpm --import MIDGARD-RPM-GPG-KEY

• For SuSE Linux 9.1:

  mkdir /etc/apt/gpg
  cd /etc/apt/gpg
  wget -O MIDGARD-RPM-GPG-KEY http://www.puv.fi/download/midgard/suse/9.1/i586/RPM-GPG-KEY
  rpm --import MIDGARD-RPM-GPG-KEY

Configure apt repository sources.

• For SuSE Linux 9.2:

  cd /etc/apt/sources.list.d
  wget http://www.puv.fi/download/midgard/suse/9.2/i586/midgard.list

• For SuSE Linux 9.1:

  cd /etc/apt/sources.list.d
  wget http://www.puv.fi/download/midgard/suse/9.1/i586/midgard.list

Run apt-get update midgard for updating the apt database (this adds our repository into your apt).

If you're going to install midcom-indexer-lucene (this package requires lucene from the jpackage-generic repository), set up apt to use the generic free repository. Instructions: http://www.jpackage.org/repos.php

If you don't have MySQL server running at local or remote host, install and start it: apt-get install mysql && /etc/init.d/mysql start

Install Midgard 1.6.x with the command apt-get install midgard. (You can update Midgard 1.6.x with the command apt-get update midgard && apt-get upgrade midgard.)

Install Midgard 1.7.x with the command apt-get install midgard-cms. (You can update Midgard 1.7.x with the command apt-get update midgard && apt-get dist-upgrade midgard-cms.)

Run datagard for setting up a new Midgard database and virtual host. Read the instructions from http://www.midgard-project.org/documentation/installation/.

Upgrading:

If you are upgrading Midgard from 1.6 to 1.7, the easiest way to do this is to run full system update command ("apt-get update && apt-get dist-upgrade").

The Midgard CMS package is now named as "midgard-cms". You have now all the control you need. Every Midgard application is now packaged as RPM and installed by RPM (no need to run datagard for importing the package - RPM does this for you).

For example: If you just want to use SpiderAdmin and nothing else, install the "spider" package ("apt-get install spider") (and run datagard's db install if this is a new Midgard install - otherwise installing the RPM is all you need to do). Or if you are a developer and want to test the development versions of the appications, install only the Midgard Framework package (called "midgard-framework") and run the datagard's db install. Then place your application (.tar* or .xml*) under /usr/share/midgard/pkgs/ and run datagard's import to install your own package.

To see which packages are available, use the search functions available in the install tool (apt-cache search <pkgname>) or browse the repository (for 9.2) at
http://www.puv.fi/download/midgard/suse/9.2/i586/RPMS.stable/ (stable)
http://www.puv.fi/download/midgard/suse/9.2/i586/RPMS.testing/ (testing)
http://www.puv.fi/download/midgard/suse/9.2/i586/RPMS.unstable/ (unstable)

If you are using other repository than stable, please note that you must enable also the stable repository (and testing if you are using unstable) to be able to have access to all available packages. The packages walk through the repository by entering unstable and exiting stable (older packages for the same major Midgard version are usually removed when a new bugfix release is published).

Remember: Do not use the unstable repository in production systems as it contains usually CVS snapshots or packages that were "just built". The testing repository is often a good choise as this enables newer versions like beta releases. But for serious production, please use the stable repository which contains the official stable Midgard release versions of the packages.

Advanced usage: The new datagard has three command arguments for power users (syntax: datagard <command>). These are:

• select - Select individual packages when installing a new database (the default behaviour is to install all packages currently available in the pkgs dir). This makes it possible to install different packages into different databases. This argument has also meaning for RPM. When installing a package with datagard that was launched using this argument, you also tell RPM to import future updates to the specific database only if the package in question is installed into that database (the default behaviour of RPM is to import the package to all Midgard databases - this is done so that you can install new packages with RPM without the need of running datagard manually afterwards).
• download - Download new/updated packages from the internet. This argument tells datagard to prompt you for selecting new/updated packages to download before installing them (affects "Install" and "Import" choises). This command is only usefull for users who use a source installation of datagard. SuSE Linux users can install/update all their applications and other Midgard packages with apt-get. The RPMS should always be at the same versions as those source packages available with this download command. Again, please note that you should not use this command in SuSE Linux as installing source packages bypasses RPM and makes RPM unaware that the package is installed. Also, with RPM you get automatic updates.
• import - This command was originally implemented to support packaging software like RPM to import the package automatically to the database when installing (updates are always imported automatically, installs are imported when you have a Midgard database in place and the select flag is off). Again, this command is pretty useless for SuSE Linux users, but for developers this provides an easy way to import a new custom xml package into the database without the need to tell datagard the answers it already knows (db,user,pass etc. - those questions need to be asked because datagard must handle situations where the db settings have changed). This command is only for importing xml packages from the /usr/share/midgard/data/ directory.

Note about SuSE Linux 9.2 and php4-dba: SuSE Linux 9.2 does not contain php4-dba package. We have therefore packaged it for you. It will be installed when you install a package which requires it.