On Thu, 21 Jun 2007, John W. Eaton wrote:
Really? Even if the installer is not linked with the GPLed program
that is installing? Why? I thought the GPL covered derivative works.
How would an installer program be a derivative work of the program it
installs?
From GPL v2:
"The source cod
On 21-Jun-2007, Bob Friesenhahn wrote:
| You are correct that a strict interpretation of GPL v2 does not allow
| GPLed software to be installed using anything other than an an
| open-sourced installation program which is itself licenced for
| re-distribution under a no more restrictive license
On Thu, 21 Jun 2007, herb wrote:
Hi there. I have created a Mac OS X 10.4 package that installs
Autoconf 2.61. I was wondering if it was "allowed" to have it
uploaded to the ftp site. Would it break any rules, such as the fact
that the Mac OS X "Installer" program is proprietary software? Ev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to herb on 6/21/2007 4:25 PM:
> Hi there. I have created a Mac OS X 10.4 package that installs
> Autoconf 2.61. I was wondering if it was "allowed" to have it
> uploaded to the ftp site. Would it break any rules, such as the fact
> that th
Hi there. I have created a Mac OS X 10.4 package that installs
Autoconf 2.61. I was wondering if it was "allowed" to have it
uploaded to the ftp site. Would it break any rules, such as the fact
that the Mac OS X "Installer" program is proprietary software? Even
though Installer is proprietary
Hello Jason,
* Jason Curl wrote on Wed, Jun 20, 2007 at 11:55:54PM CEST:
>
> I've searched in vain on the Web how I might run configure to use Solaris'
> 'lint' program. It appears that their 'lint' is very much like a compiler
> where it produces objects that can be linked together to form a fi
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> I think this should be applied to HEAD and branch-1-10.
> Would you like me to do it?
Yes, please. And thanks for your review; your points all look right
to me.
> So this is yet another reason to keep Autoconf version incompatibilities
> as few as p
Hello world,
* Eric Blake wrote on Thu, Jun 21, 2007 at 02:16:32PM CEST:
> According to Paul Eggert on 6/20/2007 11:36 PM:
> >
> > +[m4_warning([this file was generated for autoconf $ac_version.
> > +You have another version of autoconf. It may work, but it may not.
> > +If you have problems, yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Eggert on 6/20/2007 11:36 PM:
> Bruno Haible <[EMAIL PROTECTED]> writes:
>
>> Are we now supposed to edit Makefile.in by hand each time we modify
>> Makefile.am?
>
> I hope not. How about the following (untested) Automake patch?
L
On Wednesday 20 June 2007, Bruno Haible wrote:
> Bob Proulx wrote:
> > I would follow that clue and regenerate everything.
> >
> > autoreconf
> > ./configure
>
> Doesn't work:
>
> $ pwd
> /build/libidn-0.6.14
> $ autoreconf
> configure.ac:41: error: possibly undefined macro: AC_LIBTOOL_
10 matches
Mail list logo
