Sean Kellogg [EMAIL PROTECTED] wrote: [...]
As source code, it is not a derivative, I agree... but once it is compiled
it
is now a derivative work joining the library with the code to form the final
binary. Its the act of compilation that creates the derivative work.
Most (all?) php
4. Products derived from this software may not be called PHP, nor
may PHP appear in their name, without prior written permission from
[EMAIL PROTECTED] You may indicate that your software works in
conjunction with PHP by saying Foo for PHP instead of calling it
PHP Foo or
On Thursday 25 August 2005 02:01 am, MJ Ray wrote:
Sean Kellogg [EMAIL PROTECTED] wrote: [...]
As source code, it is not a derivative, I agree... but once it is
compiled it
is now a derivative work joining the library with the code to form the
final binary. Its the act of compilation
On 8/24/05, Ken Arromdee [EMAIL PROTECTED] wrote:
Game mechanics, methods, procedures, etc. are not copyrightable.
To the degree that their concrete implementations are a creative work,
their implementations are copyrightable.
--
Raul
On 8/24/05, Ricardo Gladwell [EMAIL PROTECTED] wrote:
The Section 7 of the OGL also states that:
You agree not to indicate compatibility or co-adaptability with any
Trademark or Registered Trademark in conjunction with a work
containing Open Game Content except as expressly licensed in
On Thu, 25 Aug 2005, Raul Miller wrote:
Game mechanics, methods, procedures, etc. are not copyrightable.
To the degree that their concrete implementations are a creative work,
their implementations are copyrightable.
But that's not what TSR means. They're claiming that if you use their game
I'd like to package the existing game LARN for Debian.
Before I send out an ITP, I'd like to clarify one issue.
The text below is what I'd currently put in debian/copyright.
Is this sufficient to enable addition into contrib or main ?
Nathan Tenny has the following note on a web page ...
7 matches
Mail list logo
