[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [aspell-devel] What should version info for a libaspell.dll contain?

From: Gary Setter
Subject: Re: [aspell-devel] What should version info for a libaspell.dll contain?
Date: Mon, 18 Sep 2006 08:09:51 -0500

----- Original Message ----- 
From: "Jose Da Silva" <address@hidden>
To: "Gary Setter" <address@hidden>
Cc: <address@hidden>
Sent: Sunday, September 17, 2006 5:49 PM
Subject: Re: [aspell-devel] What should version info for a
libaspell.dll contain?

> On September 17, 2006 12:04 pm, Gary Setter wrote:
> > I have a simple Windows program that uses aspell for it's
> > check feature. The source forge page is here:
> >
> Hi Gary,
> I think you should rather be concerned about the "GPL police"
and not
> what anyone in Aspell or any other project think.
> A basic requirement for GPL or LGPL is that the end user have
> code available so that they can modify their version of code
> you ship Aspell as-is or modify it to fit your-their needs, you
> need to ship (or make available) a copy of the Aspell "you"
used for
> your project and it needs to be complete enough that an end
user should
> be able to compile your copy without hassle.
> About the only exception I can think of right now is if you
agree with
> your upstream, in this case, Aspell, Kevin, that they provide
> necessary code version you used.
> I read a few articles about this and tried searching back, so
this is
> about as close to what you really need or care to know.
> Hopefully this is all relative food for thought:
> "GPL requirement could have a chilling effect on derivative
> or a better reference is here:
> and this:
> take particular note of what the author wrote because it points
to a
> relevant GPL/LGPL page that talks about linking to external
> > I called it version and under comments I have this:
> > "Based on Aspell 0.61 from CVS with changes for Descriptive
> > Diary project."
> > No company name, no trademark, no endearing icon.
> > Is this what you want, or should I make changes, or remove
> One of the nice things about the GPL or LGPL is that you don't
> anyone's permission to modify something to meet your needs.
> The only notable exceptions is "not to mix code" from different
> that are incompatible with each other, here is a good reference
to show
> the problems/realities of trying to keep everything "above
> If you make it for others to use, you need to provide source
> It's been a requirement since the beginning.
> If you follow other projects, you will note complete packages
as well as
> patches/changes they made to fit their needs.
> Go to and type this in the search box:
> aspell zzz patch
> where you substitute these words for zzz:
> bsd, debian, ubuntu, mandriva, memphis, ...or any other project
> distribution.
> Hopefully this covers all the details of what you want to know.

Hi Jose,

I did make the source code available. If you had downloaded the
zip file, you would have fond the the file desc_data_exes.txt
which contains this explaination:
This is a set of exectuables compiled from Gary Setters port of
the contents of CVS on savanna for aspell 0.61 on 17 Dec 2005. It
also includes the executable for the Diary program which uses
this port for its spell check function.
The source for diary and the port can be found at
Aspell is licensed under the LGPL. Diary is licensed under the
The software is in alpha release status.

A binary distribution along side a source code distribution is
normal. However, if there are objections to what I have done, I
will remove it, no justification is necessary on the Aspell Crews

If however you have an idea of how this could be done better I'm
eager to respond to that as well.

Best regards,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]