"Ken" <tyl### [at] pacbellnet> wrote:
>
> Well, it seems we have a solution here. You can use the source code to
> compile your own console version. The POV-Team will continue providing
> POV-Ray as they have. When you compile your own console version you
> do so with the full knowledge that you will use if explicitely for your
own
> purposes and will not distribute it publically. I honestly don't see where
the
> problem is.

Sure, there is no problem. I just tried (w/o much luck, as I see, in that no
one got it; my language problem?) to say that *if* there were an official
console version, it would make my life easier. I did not say that since
there are no official Win32 console version, I have a problem... No.

<completely different matter>

It is my understanding that if I ever decide to distribute my programs
(either publicly or just to a selected people; BTW, currently, I distribute
just the results of their work, so to say) altogether with the custom
version of POV-Ray, I have to do the following:
1) make complete sourse code (== all my modifications) of the custom POV-Ray
version publicly available,
2) make sure that each time my software runs POV-Ray, this fact is
prominently presented to the user of said software, by whatever means.
3) include original POV-Ray legal and authorship information.

Current scheme looks like this: when my software runs POV-Ray, respective
message appears on its console. The POV-Ray itself resides in the bin
subfolder, altogether with povlegal.doc and povwhere.txt files. If run by
itself (povray.exe), it displays all the credits and copyright information,
just as an official version does. The version is clearly marked as
"Unofficial Win32 Console (x86)..." etc.

I acknowledge that I'm currently the only user of my custom version of
POV-Ray and that, as soon as I pass it to anyone esle, I will make the
complete source code publicly available.

</completely different matter>

Post a reply to this message