Re: Concluding the LPPL debate, try 2
>> Why? If a file is outside the LaTeX search path, there is no reason to
>> keep it frozen. Actually the current LPPL explicitly gives you the
>> right to change a licensed file without renaming it, if you place it
>> outside of the LaTeX search path. It does not recommend it, but is
>> allowed nevertheless.
> Could you please give a more precise reference, preferrably a quote,
> of the language you think allows this?
LPPL 1.2 isn't exactly clear on this point but the intention is that it
is allowed. LPPL does refer nomatively to modguide (the latex
modification guidelines) for details on modification of latex
The relevant bit of modguide is here (note the ^^^^^^^^^^)
It would be reasonable to argue that this bit of modguide isn't exactly
consistent with parts of LPPL but if so that is an error that can be
fixed.
David
It is possible that you need to produce a document processing system
based on standard \LaTeX{} but with functionality that cannot be
implemented by using the approved configuration files and complying
with the restriction on the code that is allowed in them. In other
words, you may need a system which is sufficiently distinct from
Standard \LaTeX{} that it is not feasible to do this simply by using
the configuration options we provide or by producing new classes and
packages.
If you do produce such a system then, for the reasons described
above, you should ensure that your system is clearly distinguished
from Standard \LaTeX{} in every possible way, including the following.
\begin{enumerate}
\item
Give your system a distinguished name, such as \nstex, which clearly
distinguishes it from \LaTeX{}.
\item
Ensure that it contains no file with a name the same as that of
a file in the standard distribution but with different contents.
(If this is not possible then you must:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
\begin{itemize}
\item
ensure that files from the non-\LaTeX{} system cannot be
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
accidentally accessed whilst using a standard \LaTeX{};
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
\item ensure that each file from the non-\LaTeX{} system clearly
identifies itself as a non-\LaTeX{} file on the terminal and in the
log file.)
\end{itemize}
\item
Ensure that the method used to run your system is clearly
\label{mcon:command}
distinct from that used to run Standard \LaTeX; e.g.~by using a
command name or menu entry that is clearly not \texttt{latex}
(or \texttt{LaTeX} etc).
\item
Ensure that, when a file is being processed by your system, the
use of non-standard \LaTeX{} is clearly proclaimed to the user by
whatever means is appropriate.
\item Ensure that what is written at the beginning of the log file
clearly shows that your system has been used, and that it is
not Standard \LaTeX{}.
See the file \texttt{cfgguide.tex} for how to achieve this.
\item
Clearly explain to users that bug reports concerning your
system should not be sent to the maintainers of Standard
\LaTeX{}.
\end{enumerate}
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.
--
To UNSUBSCRIBE, email to debian-legal-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: