caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: "chris.danx" <chris.danx@ntlworld.com>
Cc: Olivier Andrieu <andrieu@ijm.jussieu.fr>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] WxWidgets?
Date: 17 Sep 2004 23:51:23 +1000	[thread overview]
Message-ID: <1095429082.2580.38.camel@pelican.wigram> (raw)
In-Reply-To: <414AE28B.8050602@ntlworld.com>

On Fri, 2004-09-17 at 23:11, chris.danx wrote:
>  
> > GTK+ is perfectly fine for commercial applications, it's licensed
> > under the LGPL.
> 
> That wasn't the problem.  The problem is L&F.

Which means 'look and feel' :)

LGPL isn't fine if you statically link OR #include
any GTK headers. That makes your binary a derived
work. It says so in the LGPL licence. So your
*source* may not be LGPL, but the resultant 
program is.

Then this clause applies, and it is anything but
what is required for a commercial situation,
where typically 'totally unencumbered' is the only
viable position:


  6. As an exception to the Sections above, you may also combine or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.
                                                                                
  You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License.  You must supply a copy of this License.  If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License.  Also, you must do one
of these things:

[....]

-- 
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850, 
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net



-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2004-09-17 13:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 20:08 chris.danx
2004-09-16 20:25 ` Richard Jones
2004-09-16 21:29   ` chris.danx
2004-09-16 21:39     ` Richard Jones
2004-09-16 22:00       ` Daan Leijen
2004-09-17  0:06         ` SooHyoung Oh
2004-09-17  4:39           ` skaller
2004-09-17  7:13           ` Daan Leijen
2004-09-17  8:04             ` Jean-Marc EBER
2004-09-19 21:46         ` François-Xavier HOUARD
2004-09-16 23:58       ` chris.danx
2004-09-17  8:10         ` Richard Jones
2004-09-17 12:38     ` Olivier Andrieu
2004-09-17 13:11       ` chris.danx
2004-09-17 13:51         ` skaller [this message]
2004-09-17 18:31           ` Brian Hurt
2004-09-17  7:53   ` Benedikt Grundmann
2004-09-16 20:44 ` Micha
2004-09-16 20:56 ` Basile STARYNKEVITCH
2004-09-20  1:02 ` [Caml-list] WxWidgets? - wxcaml SooHyoung Oh
2004-09-21 23:21   ` Zeno

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1095429082.2580.38.camel@pelican.wigram \
    --to=skaller@users.sourceforge.net \
    --cc=andrieu@ijm.jussieu.fr \
    --cc=caml-list@inria.fr \
    --cc=chris.danx@ntlworld.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).