On Wed, 10 May 2000, Bill Gribble wrote:
> You can't even put it on a CD that you sell for $5. And saying "you
> have to go download mySQL to be able to use this product" is (IANAL)
> equivalent to selling it with the product, if a lawyer wants to get on
> your butt about it.
>
> > I again repeat. The capabilities of MySQL (and others) ARE ADEQUATE
> > for a large portion of the userbase. Support for them should not be
> > rejected simply because they don't meet the needs of everyone.
>
> There *are* free alternatives. Free in this case means that if we
> make gnucash depend on it, we don't restrict people's abilities to use
> and distribute gnucash.
The distinction is in "requires" and "can use".
I (also) ANAL, but believe that there is nothing which precludes you for
including explicit instructions on how to download and install MySQL for use
with gnucash (or any other product).
Fundamentally, the tradeoff is between "self contained" and easy/efficiency
of use.
What I DON
What I DON'T want to see is gnucash relying on ANY particular DB.
Reisfs or jfs might be a better solution in some cases. After all, we are
using simple files right now and THEY WORK for many users.
As much as some people might like to think differently, you really NEED much
more expensive solutions to get the value that some people are CLAIMING that
they get from Linux/PostgreSQL.
Don't EXCLUDE other less-than-perfect solutions based on this FUD.
