> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm.poure@freesurf.fr]
> Sent: Friday, May 10, 2002 8:29 PM
> Robert Collins wrote me to explain quite a few tricks about
> Cygwin setup.exe
> installer:
>
> 1) Latest CVS Cygwin setup.exe supports scripting. I don't
> know in what extent
> installation features are mapped. At least, this means we
> should try the
> latest CVS version.
Actually, the last 3-4 versions have all supported scripting and dependencies. There's currently a nasty parser
overflowbecause the setup.ini got too big, but I've just fixed this and am committing a CVS fix asap. Certainly I
encourageexperimentation and am happy to discuss what can be done. The official setup.exe mailing list is
cygwin-apps@cygwin.com.Currently there are ~4-5 folk actively contributing setup.exe code, so things that take someones
interesthappen fairly quickly.
> 2) setup.exe is not needed if you know WHICH packages are
> required (with no
> relation to scripting). You simply need to provide path and
> everything in a
> proper setup.ini file. Et voilà.
The KDE on cygwin group use this approach (they distribute binaries via a setup.ini site, but don't distribute
setup.exeat all). You simply add a user URL to setup.exe when you run it, and it picks up your package, merges it into
thelist, and will install any needed packages from any other site as listed by your 'requires:' statement.
> 3) setup.exe supports post-installation scripts. This may
> allow us to make a
> minimal PostgreSQL install of Template1, enable a TCP/IP
> socket, etc...
> inside a Cygwin package (example : run a bash script or
> connect locally using
> SSH to su under postgres user). Otherwize, we could do it
> manually using an
> installer script.
Yes. Also setup supports pre-removal scripts, to allow tidying things up.
Cheers,
Rob
