Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 03 Feb 2004 13:57:03 -0500
From: Alan Dobkin <Cygwin AT OmniComp DOT Org>
To: Cygwin Mailing List <Cygwin AT cygwin DOT com>
Subject: Re: Modular setup?
Message-ID: <1466661703.1075816623@[192.168.70.4]>
In-Reply-To: <Pine.GSO.4.56.0402031155480.24268@slinky.cs.nyu.edu>
References: <401EF4CF DOT 9010300 AT cs DOT york DOT ac DOT uk> <1075812281 DOT 1481 DOT 8 DOT camel AT localhost> <1456737390.1075806699@[192.168.70.4]> <Pine DOT GSO DOT 4 DOT 56 DOT 0402031155480 DOT 24268 AT slinky DOT cs DOT nyu DOT edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-IsSubscribed: yes

--On Tuesday, February 03, 2004 12:29 PM -0500 Igor Pechtchanski 
<pechtcha AT cs DOT nyu DOT edu> wrote:

> On Tue, 3 Feb 2004, Alan Dobkin wrote:
>
>> My main goal is to be able to automate Cygwin installations on new
>> machines so someone doesn't have to manually select each package in
>> the GUI. I don't think this can be done with the existing command
>> line options to the GUI, but please correct me if I'm wrong.
>
> Create a custom local mirror where all the packages you want to be
> installed by default are in the "Base" category, and then use setup
> in unattended mode.
> 	Igor

I thought about doing this, especially since I already have my own
local mirror, however it seems like this would entail *way* too much
manual effort to keep it up to date.  New and updated packages are
released on almost daily basis, so I would have to recreate my custom
setup.ini file constantly to reflect the new files in the mirror.  Of
course, I could create a script to do that for me, but then it might
as well just be a script to operate against any (non-custom) mirror,
which is why something like cgf's cygupdate seems like a better answer.

I suppose, alternatively, I could do what you suggested with a static
set of packages in a custom mirror, then run setup in unattended mode
a second time against a standard current mirror.  This should work with
limited maintenance effort, but it requires setup to be run twice for
each installation, which I'd rather avoid by just getting the selected
packages directly from a standard current mirror to begin with.

A third option would be to add another parameter to the setup program
that would allow individual packages (and optionally categories) to be
specified on the command-line or read from a text file.  This would be
ideal, since it would already support all of the features that setup
provides, especially package dependencies, in-use files, and the fact
that it is a self-contained executable (i.e. doesn't require perl or
any cygwin packages to be installed for it to run, unlike cygupdate).
If I find enough time to write patches, this is probably the way to go.

Alan

--
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/