Date: Fri, 9 Sep 2011 16:31:52 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: automated cygwin install
Message-ID: <20110909203152.GB6385@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <6p4k675lc62jj9ngemb18v2h94mpnjcpsu AT 4ax DOT com> <4E6A6863 DOT 2030600 AT etr-usa DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4E6A6863.2030600@etr-usa.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Fri, Sep 09, 2011 at 01:26:27PM -0600, Warren Young wrote:
>On 9/9/2011 7:52 AM, Andrew Schulman wrote:
>> Here's what mine looks like:
>>
>> setup.exe ^
>> --no-shortcuts ^
>> --quiet-mode ^
>> --disable-buggy-antivirus ^
>> --packages ^
>> aria2,^
>> atool,^
>> autoconf,^
>> automake,^
>> autossh,^
>
>Step 2: A script that can write out such a script to clone an existing 
>installation.  Just translate the contents of /etc/setup/installed.db to 
>the form --packages wants.

>Step 3: Modify the script to find the last-used setup.ini (registry?), 
>put the packages there into a dependency graph, then compute the minimum 
>set of packages needed to clone the installation.

I was thinking about that too.  Don't you get into potential trouble
when dealing with packages whose name also reflects their version
like libncurses?

>No, I am not volunteering. :)

I might volunteer.  This has come up often enough that it seems like
it would be a useful thing to have.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple