From: | Glenn Murray <gmurray(at)mines(dot)edu> |
---|---|
To: | Jason Tishler <jason(at)tishler(dot)net> |
Cc: | cygwin(at)cygwin(dot)com, <pgsql-cygwin(at)postgresql(dot)org> |
Subject: | Re: Simplifying Cygwin PosgreSQL Installation |
Date: | 2002-10-22 22:46:51 |
Message-ID: | Pine.LNX.4.44.0210221610500.1004-100000@beautiful.mines.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-cygwin |
Jason,
Thank you very much for your reply, I am learning a lot already.
Keep in mind that my goal is to simplify installation of Cygwin
PostreSQL, not to mention cygipc. The difficult part of the install
is navigating through the setup.exe dialogs. Your Suggestion #2
reproduces that problem and your Suggestion #3 makes it harder. Only
your Suggestion #1 might simplify this by enabling me to tell the user
to "Hit the `Next' button until done", so let me ask about that.
By "Create a minimal Cygwin mirror" do you mean create a space on a
web server and put files (as described in
http://cygwin.com/setup.html) that setup.exe can find? I did a search
in cygwin-apps for "upset" and found lots of references but not an
explanation. I take it that upset helps build a setup.ini file which
gets downloaded from the mirror. Where do you get it? I didn't find
"upset" as a cygwin package.
How does setup.exe see this mirror and not the official Cygwin
mirrors, i.e., how do I "point my Windows users" to that particular
mirror?
Thanks again,
Glenn Murray
http://www.mines.edu/~gmurray
On Tue, 22 Oct 2002, Jason Tishler wrote:
> Glenn,
>
> On Tue, Oct 22, 2002 at 11:14:36AM -0600, Glenn Murray wrote:
> > It seems that the best solution would be to provide a self-contained
> > Cygwin PostgreSQL installation that works independently of a
> > previously existing installation.
>
> The above is not possibly because it violates the one Cygwin DLL per
> system restriction.
>
> > Comments or solutions?
>
> Suggestion #1:
> =============
>
> 1. Package your software as a Cygwin setup.exe installable tarball.
>
> 2. Automate the installation steps in the Cygwin PostgreSQL README:
>
> http://www.tishler.net/jason/software/postgresql/postgresql-7.2.3.README
>
> as a shell script and post it to cygwin(at)cygwin(dot)com(dot) I will add this
> script to the Cygwin PostgreSQL distribution as a postinstall script, if
> done properly.
>
> 3. Create a minimal Cygwin mirror plus your package and cygipc using
> upset to generate a setup.ini file that matches your mirror. Search
> cygwin-apps@ for info regarding upset. Search the pgsql-cygwin@
> archives for the (incomplete) work done to determine the minimum Cygwin
> packages required by PostgreSQL.
>
> 4. Point your Windows users to your mirror and instruct them to use
> Cygwin's setup.exe to install the software.
>
> Suggestion #2:
> =============
>
> 1. Same as above
>
> 2. Same as above
>
> 3. Contribute your package to the standard Cygwin distribution.
>
> 4. Same as above but point your Windows users to any Cygwin mirror.
>
> Suggestion #3:
> =============
>
> 1. Same as above
>
> 2. Same as above
>
> 3. Same as above but create a (partial) mirror that only contains your
> package and cygipc.
>
> 4. Same as above but point your Windows users to any Cygwin mirror plus
> your mirror. Note that Cygwin's setup.exe can install from multiple
> mirrors simultaneously.
>
> Although the above suggestions may be more work than desired, it will
> guarantee that your software will always coexist nicely with the
> standard Cygwin distribution.
>
> Jason
From | Date | Subject | |
---|---|---|---|
Next Message | Florian Litot | 2002-10-23 07:39:00 | launch a request |
Previous Message | Jason Tishler | 2002-10-22 19:29:13 | Re: Simplifying Cygwin PosgreSQL Installation |