|
 |
Actually, after reading POVLegal for the first time, I found that there is
no such restriction on suppressing credits & copyright messages. The
program (if redistributed) must only be freeware, source code publically
available, support it yourself, etc. In a "custom version", all existing
features must be intact... put banners/copyright into --version or -v
option? Also, "The source distribution is provided to; ... 2) promote
experimentation and development of new features to the core code which might
eventually be incorporated into the official version."
Finally, POVLegal applies to POV-ray as freeware and not public-domain.
Would POV-ray be public-domain if it were made open-source?
Jason
"Pabs" <pab### [at] hotmail com> wrote in message
news:39F8DDA9.F18EFE7A@hotmail.com...
> Warp wrote:
>
> > Steve <ste### [at] zeroppsuklinuxnet> wrote:
> > : Pov already has command line options.
> >
> > He wasn't talking about command line options but proper return values
>
> 0 for success & 1 for failure?
>
> > and text output (and quietness if no error happened).
>
> Suppressing the credits & copyright messages?
> Sounds contrary to POVLegal to me.
> Correct me if I'm wrong.
> --
> Bye
> Pabs
>
Post a reply to this message
|
|
|
|
Pabs wrote:
>
> Suppressing the credits & copyright messages?
> Sounds contrary to POVLegal to me.
> Correct me if I'm wrong.
> --
> Bye
> Pabs
There are principles behind POVLegal, and this
copyright file in fact lists the rules that are
deduced from these principles.
One of these is that the presence of POV-Ray
should not be hidden to the user. No one is to
create a program and make the user believe the
3D-rendering part is his own work.
The rules that derive from this principle are:
* you can't turn POV-Ray to a DLL, because then
people would think the author of the front-end
(e.g. a modelling software) to also be the author
of the "part that does the 3D stuff".
* you can't run a web interface to POV-Ray
without saying prominently that this is POV-Ray.
Once again, so that people know who did the "hard"
work.
* probably others I don't remember.
Now, we want to see if making POV-Ray sort-of
"GNU-compliant" as for the command line is
compliant with the principle. Because indeed
it "could" hide the fact that POV-Ray is called
inside a script.
If it is, I don't think there will be much
trouble. If fear arises that some wording in
POVLegal is against that, perhaps this can
be discussed with someone of the POV team.
---
One way to achieve that, I think, is to allow the
user, for each of the seven text streams, to choose
between a file, stderr, or stdout. You could then
choose in your shell scripts (or makefile, but I'm
not experienced in that) to send stdout or stderr
to /dev/null.
Post a reply to this message
|
|
