[Radiance-dev] Re: Radiance in Debian
Randolph Fritz
randolph at panix.com
Fri Oct 26 20:33:37 PDT 2007
Mmmmm...I'll put forward my suggestion again as probably the best way
to both satisfy Debian's namespace requirements and keep existing
scene descriptions--the ".rad" language, really--working. I'd go for
putting the binaries in /usr/lib/radiance as a simple way to get them
out of the main /usr/bin namespace; it is not terribly hard to add
that to your path and I've been doing something similar for a very
long time.
Randolph
On Oct 26, 2007, at 9:45 AM, Gregory J. Ward wrote:
> Well, I'm in a quandary on this, because I don't know how valuable
> having a Debian package is to the Radiance community relative to
> breaking most of the existing scene descriptions, if that's what it
> means.
>
> -Greg
>
>> From: Bernd Zeimetz <bernd at bzed.de>
>> Date: October 26, 2007 9:39:53 AM PDT
>>
>> Hi Greg,
>>
>> sorry for the late reply, just didn't find the time before.
>>
>>> Having compatibility links as an option during installation is
>>> fine with
>>> me if it defaults to "yes" or provides a clear explanation of the
>>> pitfalls of not installing the links. I guess we only need a
>>> link for
>>> genbox at this point, though I would like to keep "rview" in
>>> there as
>>> well for consistency with extant documentation.
>>
>> They can't default to yes as they'd be added in automatic testing
>> environments (where all debconf questions are answered with the
>> default
>> value) and installing the conflicting package could fail then.
>>
>> I'm all open to other suggestions, we should find the final solution
>> within the next months, though.
>>
>> Cheers,
>>
>> Bernd
>>
>> --
>> Bernd Zeimetz
>> <bernd at bzed.de> <http://bzed.de/>
>
> _______________________________________________
> Radiance-dev mailing list
> Radiance-dev at radiance-online.org
> http://www.radiance-online.org/mailman/listinfo/radiance-dev
>
More information about the Radiance-dev
mailing list