clipka <ano### [at] anonymousorg> wrote:
> Am 25.09.2017 um 05:01 schrieb Kenneth:
> >>
[Clipka wrote:]
> >> Be advised that this binary-only release wants to reside in an existing
> >> v3.7.x installation.
> >>
> > So, it seems that installing this into v3.7.1 beta 9 (which is
> > a 'stand-alone' version of Pov-Ray) is OK to do(?)--
>
> Technically, it should work best with any POV-Ray v3.7.x release proper
> - which de facto means v3.7.0. (POV-Ray v3.7.1-rc1 should also work
> fine, but that installer is no longer officially available.)
>
> It /may/ work ok with any v3.7.x-beta, but it isn't designed to do so,
> and there may be subtle problems arising out of it - stuff like being
> unable to find certain files, or loading a file from an unexpected
> directory.

Well, I'm learning something new every day ;-) Thanks for the clarification (and
I hope I understand it all.) For one thing, it seems that I've been erroneously
assuming "3.7x" and "3.7.x" to mean the same thing. (I've always used those
interchangably-- including "3.7xx"-- as a kind of lazy 'shorthand', in my own
mind and here in the newsgroups, for the same meaning-- not realizing that they
may have different meanings technically.) And yes, I've already run into the
'loading of a file from an unexpected directory' problem, in some of the
previous alphas/betas-- due no doubt to my lazy/hazy understanding of the
underlying processes.
>
> The background there is that POV-Ray for Windows uses a portion of its
> version number in directory names and registry keys, namely `vX.Y`
> (which I refer to as the "generation") for any POV-Ray vX.Y.Z final
> release.
[snip]

Thanks. I definitely don't want to screw up the registry! (OR my current beta 9
install.)

SO...I'll stick to installing this newest version into 3.7.0 proper.

Post a reply to this message