Re: PostgreSQL without cygwin.

From: Jason Tishler <jason(at)tishler(dot)net>
To: Ben Clewett <B(dot)Clewett(at)roadrunner(dot)uk(dot)com>
Cc: Pgsql-Cygwin <pgsql-cygwin(at)postgresql(dot)org>
Subject: Re: PostgreSQL without cygwin.
Date: 2003-02-18 17:59:35
Message-ID: 20030218175935.GJ2332@tishler.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-cygwin

Ben,

Please keep your replies on-list.

On Tue, Feb 18, 2003 at 04:37:31PM +0000, Ben Clewett wrote:
> Jason Tishler wrote:
> >Sorry, the above is not really practical. Two different Cygwin
> >versions cannot co-exist on the same system due to shared memory that
> >is version checked.
>
> Yes, I have been doing some research and found this to be true. Not
> only that, but all Cygwin seem to have a common / root file system and
> mount points. I have found a fork of CygWin which counters this, and
> I belive hacking CygWin it's self to avoid these problems is almost
> trivial. But not looked yet...

It is. Search the Cygwin ML (from today) for how to accomplish the
above.

> >>If this was possible, then an entire instalation could be embedded
> >>into a 2Mb image which could be (as I want) attached to an
> >>application for download over the Internet.
> >
> >Please don't violate the GPL if you do the above.
>
> Absolutelly not. We use much GPL software here in our solutions, and
> adherance to the GPL is paramount. Including GPL software is not too
> hard in an Install Sheild type instalation with commercial software.
> Listing the software, printing then GPL licence, and giving a URL of
^^^^^^^^^^^^^^^
> where the sourse code can be obtained, is usually enough.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I'm sorry to inform you that a URL is *not* sufficient. The easiest way
to adhere to the license is to put the source tarballs on same the
website that hosts the binaries. Note that you can encourage the user
to download the source from an alternate place, if your bandwidth is
metered.

Please don't shoot the messenger.

> Unless PostgreSQL has a different take on the GPL, in which case I
> would want to know now how PostgreSQL expect commercial software
> companies to use their products. I would hope it's not in the same
> way as MySQL, which we have had to dump becuase of their take on GPL.

No PostgreSQL does not have a different take. It is the normal GPL
license *and* Cygwin's take that is relevant here.

Jason

--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6

In response to

Browse pgsql-cygwin by date

  From Date Subject
Next Message Jason Tishler 2003-02-18 19:29:04 Re: Permissions or initdb failure?
Previous Message Jason Tishler 2003-02-18 17:13:15 Re: pgsql-cygwin