[lazarus] Delphi 5 prices!!!

michael at tfdec1.fys.kuleuven.ac.be michael at tfdec1.fys.kuleuven.ac.be
Wed Jul 21 06:18:53 EDT 1999




On Tue, 20 Jul 1999, Derk Benner wrote:

> 
> ----- Original Message -----
> From: P Jean dit Bailleul <jeanditbailleulp at em.agr.ca>
> 
> >It depends on the kind of licence of lazarus. If every lazarus application
> >must be disrtibuted with all sources, i'm sure that it this will pull away
> >a lot of compagnies.
> >For example, I'm sure that I won't be able to make my boss agree on the use
> >of lazarus in this case even if I'm sure that over 99.99% of the user won't
> >be able to use the source to do anything.
> 
> I don't mind distributing FPC and GTK+ sources, nor do I mind distributing
> full Lazarus and my app source when I'm using Lazarus/FPC to create a custom
> app for a single business.  They are paying for my time and effort and will
> quite likely want to be able to maintain the app on their own.  However, I
> would like to be able to choose to restrict custom components I create for
> Lazarus for more widespread sales.  Even then, I'd probably go with free
> binaries and a one-time fee for binaries/source of *MY* custom components.
> Whether this meets Open Source, I'm not sure, but after reading the Open
> Source article, I *think* it does.

This is essentially correct; your custom compononts link in the RTL, FCL
and whatever, but they are still separate from it. As such you can choose
not to disclose them.

You cannot do this with the lazarus components of course.

Be also aware that distributing the lazarus code, and not the code for your
components, is of no use: If the user changes lazarus components that your
code depends on, he must recompile your components to be able to work with
it. If you don't give the source, your customer has a problem :)

This has some imprortant consequences concerning versions of the RTL/FCL/GTK
and so on that Lazarus distributes; but these can be discussed later.

Michael.






More information about the Lazarus mailing list