[Radiance-general] DEB and RPM Radiance linux packages page updated!

[Francesco Anselmo]

My Radiance linux/i386 packages page has been updated:

http://dream.unipa.it/dream/pub/dot/anselmo/radiance/packages/

Here you will find the following versions of Radiance
Radiance 3.5.0
Radiance 3.5.0 static
Radiance 3.4.1 pmap 
(patched with the photon mapping extension by Roland Schregle)

I have decided to prepare 4 kinds of packages: tar.gz, tar.bz2, deb and rpm.

The tar.gz and tar.bz2 packages can be considered add-on packages, so
the suggested installation location is /opt/radiance.

The deb and rpm packages behave this way:

the binaries are installed into -> /usr/lib/radiance/bin
the radiance library is installed into  -> /usr/share/radiance/lib
the examples are installed into -> /usr/share/radiance/obj
the documentation is installed into -> /usr/share/doc/radiance
the man pages are installed into -> /usr/share/man

After the package installation, the user only has to add /usr/lib/radiance/bin
to the PATH environment variable, since I have added /usr/share/radiance/lib
to the default library search path in the source code (src/common/paths.h).

Georg Mischler wrote:
> I'd say ignore the "should"s at will. Nothing a user can do with
> your Radiance package will threaten the integrity of their
> system, not even on Debian.

I finally decided to use these locations because making a debian package
means contributing to the debian distribution, that has his own policy that
must be respected. 
I also tried to use the /opt/radiance path, but the debian packaging system 
didn't behave very well in this case, so I followed the advices that came 
from the Debian side. Of course I ignored the "csh scripts
problem" and resolved the "environment variable problem" by adding  
/usr/share/radiance/lib to the default library search path in the source code 
(src/common/paths.h), as I already said.

The rpm packages are derived from the deb ones using alien.

Here are a few notes about the packages (for more info, just check the page):
1) when compiling the "static version" I had some problems with unresolved 
symbols inside libGL.a and libGLU.a coming from the Mesa distribution. I even 
compiled by myself the Mesa libs, but this didn't solved the problem. 
Unfortunately I don't much have time to go deeper, so the static version has 
no OpenGL related stuff.
2) I never managed in compiling the pmap patched code together with
the holodeck files, so the pmap package has no holodeck executables.
If anybody wants to help me, I can share my stderr.

Many thanks to Georg Mischler and to Peter Apian-Bennewitz for their
help and comments.

I hope that these packages can be useful ...

-- 
ing. Francesco Anselmo
anselmo@dream.unipa.it
--
[ DREAm ] 
Dipartimento di Ricerche 
Energetiche e Ambientali
--
Universit� di Palermo
--
Viale delle Scienze
90128 Palermo - Italy
--
Tel + 39 091 236 302
Fax + 39 091 484 425
--