On Wed, 15 Nov 2006 23:04:40 +0100 Diego Biurrun wrote:

> On Wed, Nov 15, 2006 at 08:28:24PM +0100, Francesco Poli wrote:
[...]
> > Hence, I think the Right Thing(TM) to do is properly documenting
> > where the file `mmx.h' came from (that is to say: FFmpeg) and which
> > is the license the project we borrowed it from is available under
> > (that is to say: the GNU (L)GPL).
> > Once this is clearly documented in the debian/copyright file, I feel
> > that the issues with mmx.h will be solved.
> 
> I didn't slap a license header on the newly created mmx.h on purpose.
> Assuming that such a thing could be copyrightable is just plain silly.

I'm not saying that you should insert a copyright and permission notice
*inside* the `mmx.h' file: I'm just suggesting that you document where
it came from and that the work you took it from is available under the
GNU GPL.  This could well be documented in a separate file (for the
Debian package the right place is the debian/copyright file, for the
upstream package some README file could do...).
Once this is done, we can stop guessing about the copyrightability of
`mmx.h', I think...

I hope this clarifies.

-- 
But it is also tradition that times *must* and always
do change, my friend.   -- from _Coming to America_
..................................................... Francesco Poli .
 GnuPG key fpr == C979 F34B 27CE 5CD8 DC12  31B5 78F4 279B DD6D FCF4

Attachment: pgp3r0c5NgtUN.pgp
Description: PGP signature

Reply via email to