These packages are build by the Department of Computer Science at the
Otto-von-Guericke University Magdeburg, Germany.

They are provided on a AS IS base and there is no guarantee, that the SW works
as expected. So use on your own risk! Also note, that all stuff in any sub
directory is subject to change at any time, so downloading it may give you
even un-finished packages!

IPS packages are the primary target now. Thus SVR4 packages are only used as
intermediate build targets and are seldom installed in our environment, i.e.
only where relocation is required. Usually all SVR4 packages are relocatable
and thus can be installed anywhere using e.g. the pkgadd option '-a none'.
They binaries and scripts are usually enhanced to autodetect there location
and resolve config/resource/etc pathes to its own location. Usually there is no
real hard coded library path, however, 32bit binaries usually have relative
RPATH of $ORIGIN:$ORIGIN/../lib and 64bit binaries $ORIGIN:$ORIGIN/../lib/amd64
($ORIGIN gets resolved to the binaries location on the fly). So if you use more
than a single package, you should use for all packages the same base directory
(e.g. /local/usr or /opt/sfw).  Than everything should work out of the box
and no special LD_LIBRARY_PATH[32|64] or crle settings are needed.

Basically the same counts for IPS packages, however, since IPS allows NO
package relocation, the dyn. pathes from SVR4 packages get usually replaced
by /local/usr before they get IPS packaged. Only those, which are usually 
needed on the local file system to guarantee certain system services or
Oracle Solaris package replacements like sendmail, libmilter, etc.
will use the same base directory as its original - usually /usr/.

To use this server as an IPS package server to directly install and
automatically update packages, just issue the following command and make sure,
that your firewall allows access to it:

	pkg set-publisher --add-origin http://pkg.cs.ovgu.de/lnf 


Updates/News:
-------------
Packages are created/updated on-demand. Unarchived packages should be considered
as "work in progress".  Archived packages, i.e. *.pkg and *.pkg.{gz|xz} can be
considered as stable/fixed, if they are older than 2 weeks. If you have any
questions, ask admins+ips@cs.ovgu.de and we'll answer ASAP.

Per default we do not keep copies of obsolete/superseeded packages. However,
if you are lucky, you may find an old package in obsolete/ during a transition
period. The IPS repository keeps usually older packgages with different
component versions, however, from time to time it gets cleaned up and
"redundant" packages get removed. So if you wanna keep stuff forever, please
use a mirror for it.