[Bug 484386] Review Request: gri - A language for scientific illustration

bugzilla at redhat.com bugzilla at redhat.com
Tue Jul 14 16:39:04 UTC 2009


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=484386





--- Comment #15 from D Haley <mycae at yahoo.com>  2009-07-14 12:39:03 EDT ---
Hi Dan,

> I do think it is better for me to
> use my time on the code, rather than on reading documents about licenses.

Fair enough. So I have put together a quick and dirty script to make life a
little easier:
http://dhd.selfip.com/427e/gri-relic.tar.gz

The script allows you to choose from GPL2,GPL2+,GPL3 or GPL3+, and will modify
the source files, without changing the timestamps (Not sure this is a 100% good
idea. This may affect cvs behaviour, you will have to force a commit of all .cc
and .hh files with the -f flag, see CVS manpage). It  replaces the COPYING file
and license.txt

I also include a quick GPL intro as a printf statment in gri.cc, as well as
modifying the README-linux-redhat and README-SunOS5 files, depending upon
licence version. I don't touch the .el file -- you may need to ask your
co-author about that licence and modify (just change the GPL version number in
the .el file).

The patches apply cleanly to the release version, not the CVS. But the patches
are only very minor. Changes should be obvious from looking at them.

To use the script, untar it into your gri folder
$tar -zxvf PATH_TO/gri-relic.tar.gz
$./relic/gri-license.sh

Each time you run the script it will prepend the GPL boilerplate, so take care
only to run it once :) 

As always please check the script to make sure I am not doing anything
particularly stupid that may damage your build or system. As I have limited
time at the moment, I have not tested this very much, so your mileage will
vary.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.




More information about the Fedora-package-review mailing list