At 08:25 27/10/2007 -0700, you wrote:
On Tue Oct 02 13:39:30 2007, [EMAIL PROTECTED] wrote:
> Parrot is no longer licensed under the GPL directly (though it is
> available under the GPL through the Artistic 2.0). Update or remove
> references to the GPL license in these files:
>
> debian/copyright:45
Removed mention of some no-longer-existing files in r22523.
The other copyrights mentioned are:
lib/Digest/Perl/MD5.pm:
Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All rights
reserved.
lib/Pod/:
Copyright (c) 2001-2002 Sean M. Burke. All rights reserved.
These two will no longer be a problem when we get the external Perl
modules removed from the repository and the bundling working correctly.
languages/regex/lib/Regex/Grammar.pm:
(c) Copyright 1998-2001 Francois Desarmenien, all rights reserved.
This file is automatically generated. So what do we do with files in
such cases? It is generated from Parse::Yapp, so can we just generate
this file on demand rather than have it committed to the repository?
This copyright could be easily removed.
Currently, Grammar.pm is generated by yapp with the -s option (standalone).
So, the package Parse::Yapp::Driver is included (with its copyright) in
Grammar.pm.
Without this option, only a line "use Parse::Yapp::Driver;" is inserted in
Grammar.pm.
The constraint is now you need to install Parse::Yapp when you want use the
generated file.
François.
compilers/imcc/imcc.y, compilers/imcc/main.c, compilers/imcc/
parser_util.c,
languages/cola/:
Copyright (C) 2002 Melvin Smith <[EMAIL PROTECTED]>
Much of Melvin's stuff is co-licensed with The Perl Foundation, so can
we safely assume that the copyright here can just be updated to
Artistic 2.0?
> docs/faq.pod:159
There is only one mention of GPL here, and that is to tell people that
we use the Artistic 2.0 license and that it's compatible with the GPL,
so we don't need to worry about this file anymore.
> include/parrot/datatypes.h:4
Removed mention of the GPL in r22524.
> include/parrot/list.h:4
Removed mention of the GPL in r22525
> src/datatypes.c:3
> src/list.c:3
Removed mention of the GPL in r22526.
> Review these languages and decide whether to update the license or
move
> them to the google-code repository for Parrot languages:
>
> languages/lazy-k/calc.lazy:2
> languages/lazy-k/README:21
I don't know what to do with this language. It's not been updated in a
while. Should we move it to google-code or should it be deleted?
> languages/urm/examples/biggerzero.urm:3
> languages/urm/examples/distance.urm:3
> languages/urm/examples/div.urm:3
> languages/urm/examples/mult.urm:3
> languages/urm/examples/sim.urm:3
> languages/urm/examples/sub.urm:3
> languages/urm/README:137
> languages/urm/t/syn.t:13
> languages/urm/urmc:11
This language is all GPLd, so maybe a good canditate for being moved to
google-code. Or perhaps we could ask the author if we can license it
under Artistic 2.0? Opinions?
If you got this far through this message, thanks! :-)
Paul
