Mail Archives: cygwin/2006/08/11/11:58:46
Hi,
My intention is to develop an alternative to Cygwin Setup. That means it
must support all dependencies, setup.ini and package repositories around.
I've thought that we can have a monolithic installer which installs a basic
environment out-of-the-box. It is very convenient for most of the users. I
have already developed an experimental one with Cygwin Base (54 packages,
about 13 MB) as content. When it is ready for review, it will have a 'Cygwin
Update' function, which can be used to update existing components with
dependency check. If you want to add/remove software to/from your Cygwin
installation, then there will be a kind of 'Cygwin Boost' function, where
you can pick packages you want to install or remove.
Framework I use to develop a monolithic installer is not limited by only
'Base'. It is customizable. That means you can have different startpoints to
your cygwin installation. One variant can only have 'Cygwin barebone' to
meet needs of a specific program (rsync for example?), while the other one
can be a full-featured OpenSSH server. Cygwin Update/Boost function will be
common to all those variants of monolithic installers.
Any comments ?
Rgrds Tev
> -----Original Message-----
> From: Dave Korn [mailto:dave DOT korn AT artimi DOT com]
> Sent: Friday, August 11, 2006 5:00 PM
> To: cygwin AT cygwin DOT com
> Subject: RE: Setup.exe requirements [was RE: Cygintl-3.dll
> was not found]
>
> On 11 August 2006 15:30, Larry Hall (Cygwin) wrote:
>
>
> > It's also worth noting that the goal here was a subset of Cygwin
> > functionality packaged as a monolithic (no matter how
> small) install.
> > While the former is a potential supplement to "setup.exe",
> the latter
> > is a step backward in terms of installation flexibility.
> It seems to
> > me that any "setup.exe" replacement cannot be monolithic
> installer or
> > provide only a subset of the available packages.
>
>
> Well, just because it's a monolithic installer wouldn't
> stop it from reading setup.ini and downloading the latest
> versions of the base packages 'behind the scenes'.
>
> Perhaps the easiest solution would be a customized version
> of setup.exe that doesn't present the GUI and runs through
> the sequences of operations with everything on default settings.
>
>
>
> cheers,
> DaveK
> --
> Can't think of a witty .sigline today....
>
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -