Version 15 (modified by bruno, 12 years ago) (diff)


SVN repository Management

First you need to get the content of the SVN repository:

    # cd /to/desired/path 
    # svn checkout svn://


    # svn checkout svn://

Package build process

This is currently working for all distributions mentioned in the file tools/DISTROS (except Slackware) From the stable SVN tree extracted you need to launch:

# tools/svn2build 

which will create for you a build directory (under ../../build/stable-1) with the tar files containing the version expanded. The way svn2build works is the following:

  • It first computes the $TOOLHOME variable which is the location of the tools directory in the SVN tree
  • It then source commen-env, which sets up and creates 2 variables $TOPDIR for the delivery of the files/packages and $MONDOTMP for temporary files
  • It then source svn-env which creates 3 variables $VER which is mondo version, $REVISION which is the current SVN revision and finaly $TAG which is our package tag (what is after the - in an rpm/deb).
  • It then creates the delivery directory ($TOPDIR/$VER-$TAG)
  • Then for each package to be built (passed in parameter or taken by default as all except mindi-kernel), it exports from SVN the content of that package, seting up the REVISION file at the same time and a log file in the target directory. Then for each distro, it instantiate a build file (spec for RPM e.g.) with variables previously computed, creates the log file required for it as well, and uses m4 to create the final file based on templates under each package directory/distributions files. Those steps are distro dependent (rpm, deb and emerge)
  • Then documentation is instantiated as well (mondo-doc is always the first package in the list in order for that step to be made before as the result is used by the other packages)
  • Then mindi doc is added to the delivery directory of mindi
  • Then mondo doc is added to the delivery directory of mondo, and bootsstrap is called which will recreate the autoconf environment.
  • Finaly once all these steps are done, the tar files are created (tar.gz and tar.bz2)

then you can call

# tools/build2pkg 

in order to produce local packages for your distribution.

If you have virtual machines of other distributions that you want to generate packages for, then after setting them up following the documentation under tools/qemu-vm.txt you can call:

# tools/build2qemu 

to produce packages for all supported distros (in tools/DISTROS)

An evolution is planned for RPM packages to create hierarchies of package to ease deployment :

       |                      |              |                        |
   mondorescue-tape     mondorescue-cd   mondorescue-nfs           .....
         |                    |              |
-------------------     --------------   ---------------
|       |         |     |      |     |   |       |
mt   buffer       |     |   cdrecord     |     nfs-utils
                    |                |           |           |         |
                  mindi            afio       mkisofs       newt   syslinux

RPM rebuild process

From the sources rpm packages the nearest from your distro (that you can get from, you may build packages for your target distribution by doing:

# rpm -ivh mindi*.src.rpm mondo*.src.rpm
# rpmbuild -ba /usr/src/*/SPECS/mondo.spec 
# rpmbuild -ba /usr/src/*/SPECS/mindi.spec 
# rpmbuild -ba /usr/src/*/SPECS/mindi-busybox.spec 
# rpm -ivh /usr/src/*/RPMS/i?86/mondo*.i?86.rpm /usr/src/*/RPMS/i?86/mindi*.i?86.rpm 

File rebuild process

From the tar.gz files available under, you may build and install MondoRescue? by doing for each package:

# tar xvfz mondo*tar.gz
# cd mondo*
# ./configure
# make
# make install
# cd .. 
# tar xvfz mindi-busybox*tar.gz
# cd mindi-busybox*
# ./configure
# make
# make install
# cd .. 
# tar xvfz mindi-[0-9]*tar.gz
# cd mindi-[0-9]*
# ./
# cd ..

Location of mondo and mindi official Debian packages

Location of mondo and mindi pre-releases Debian packages

This directory contains pre-releases of Mondo Rescue Debian packages. They may not be production quality. You have been warned.

However, you are more than welcome to try them and provide feedback. Please email andree_at_debian_dot_org or preferably the Mondo Rescue mailing list at mondo-devel_at_lists_dot_sourceforge_dot_net both in case of success or lack thereof.

If you have no idea what to do with these packages, Andree suggests you just use the ones that come with Debian proper instead.

Docs for Slackware packaging

Docs for Mandriva official packaging

Docs for FreeBSD packaging

Location of mondo and mindi Files

DistributionsFile base install