Fwd: Re: libjpeg for debian, autoconf
Sorry, got the wrong mail address : here again:
Dear Debian legal, Gnu License Violation,
There seems to be a problem with the sources of
the libjpeg package. It does not have the full source code,
it is missing the autoconf and automake sources.
Do you allow debian and gnu packages to be distributed without the
"full" source code including the autoconf tools.
These sources are needed to port the package to a new platform.
Can you please advise as to the definition of source code
pertaining to the autoconf's configure.in?
> --- James Michael DuPont <firstname.lastname@example.org> wrote:
> > From James Michael DuPont Mon Oct 28 15:22:06 2002
> > Received: from [22.214.171.124] by web13303.mail.yahoo.com via
> > Mon, 28 Oct 2002 15:22:06 PST
> > Date: Mon, 28 Oct 2002 15:22:06 -0800 (PST)
> > From: James Michael DuPont <email@example.com>
> > Subject: Re: libjpeg for debian, autoconf
> > To: firstname.lastname@example.org, email@example.com
> > CC: firstname.lastname@example.org
> > In-Reply-To: <20021028231233.C21940@yellowpig>
> > MIME-Version: 1.0
> > Content-Type: text/plain; charset=us-ascii
> > Content-Length: 927
> > Dear Sirs,
> > Thank you for you great jpeg toolkit, it is very usefull.
> > I am working on porting the debian package for libjpeg to win32
> > via the mingw32 cross compiler.
> > http://introspector.sourceforge.net/dia_win32.htm
> > I have noticed that there are some automake files that are
> > configure.in, makefile.ac, and the like. These are important
> > files that are needed to port the software.
> > Can you please tell me where I can find them? the libtool included
> > in the libjpeg needs to be redone.
> > As part of the GPL, build scripts are considered source code, and
> > therefore should be distributed as such, this includes automake
> > autoconf. See section 3.
> > >> The source code for a work means the preferred form of the work
> > for
> > >> making modifications to it. For an executable work, complete
> > source
> > >> code means all the source code for all modules it contains, plus
> > any
> > " associated interface definition files, plus the scripts used to
> > control compilation and installation of the executable."
> > This in most interpretations includes the configure.in and others.
> > The creation of a configure.in and such is sometimes hard work,
> > the porting of the gtk to ming32 cross compiler is difficult, but
> > having all the sources is needed.
> > A violation of the GPL could have it removed from the debian
> > distribution and that would endanger the GTK+ toolkit and the DIA.
> > I am willing to put the work into reproducing these files if need
> > I
> > have learned to not only complain, but to also be willing to put
> > effort into solve the problem.
> > Please tell me how you want to procede.
> > Mike
> > James Michael DuPont
> > Software Developer
> > =====
> > James Michael DuPont
> > http://introspector.sourceforge.net/
> > __________________________________________________
> > Do you Yahoo!?
> > Y! Web Hosting - Let the expert host your web site
> > http://webhosting.yahoo.com/
> James Michael DuPont
> Do you Yahoo!?
> HotJobs - Search new jobs daily now
James Michael DuPont
Do you Yahoo!?
HotJobs - Search new jobs daily now