EGCG 9.0 and beyond

Peter Rice pmr at sanger.ac.uk
Fri Mar 21 04:34:32 EST 1997

In article <5gtf2c$ch3 at news.u-strasbg.fr> pingouin at crystal.u-strasbg.fr (Francois JEANMOUGIN) writes:
> As we understand it (like Fred says), you will not be able
>to distribute modified SDK source code, but you will be able to
>distribute home-made programms that uses GCG libraries.

You will need to confirm this with GCG before distributing anything.

My understanding of the SDK (having only seen an extended version) is:

2.B Use of the SDK API

  i. lets you create your own software with calls to the GCG libraries.

 ii. lets you run this (original) software.

iii. (not standard) lets you distribute this software. My understanding
     is that 2.B.iii is not in the standard SDK licence.

2.C Use of the SDK Source Code

  i. lets you adapt the source code (increased parameters, extra
     options, the usual changes).

 ii. lets you run your modified (derived) software.

iii. (not standard) allows some form of distribution. Again this is
     an extension to the standard SDK licence.

... So it appears that even code with just API calls cannot be
distributed without permission from GCG. Though I would expect that
they would give permission in practice ...

Peter Rice                           | Informatics Division,
E-mail: pmr at sanger.ac.uk             | The Sanger Centre,
Tel: (44) 1223 494967                | Wellcome Trust Genome Campus,
Fax: (44) 1223 494919                | Hinxton, Cambridge, CB10 1SA,
URL: http://www.sanger.ac.uk/~pmr/   | England

More information about the Info-gcg mailing list

Send comments to us at biosci-help [At] net.bio.net