automated cygwin install

Buchbinder, Barry (NIH/NIAID) [E]
Fri Sep 9 20:35:00 GMT 2011

Christopher Faylor sent the following at Friday, September 09, 2011 4:32 PM
>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
>>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.

The following will make the package list.

$ sed -e '1d' -e 's/ .*$//' -e 's/$/,^/' /etc/setup/installed.db

I do not think that you need Step 3.  I believe that setup will not
download or installed twice duplicates generated by package

Best wishes,

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list