Hello.
One of the simple method to install a fresh clone of the existing Cygwin's
installation is such a way:
Create a new Cygwin root install directory and etc/setup subdirectories in it,
copy therein the /etc/setup/installed.db file from the master installation you
want to clone. Then launch
Christopher Faylor sent the following at Monday, November 04, 2013 3:31 PM
On Mon, Nov 04, 2013 at 08:13:41PM +, Buchbinder, Barry (NIH/NIAID)
[E] wrote:
Lavrentiev, Anton (NIH/NLM/NCBI) [C] sent the following at Monday, November
04, 2013 1:28 PM
Thanks for the suggestion. My Systems team
Hello All,
I am trying to help my site's Systems team to straighten up CYGWIN
installation process, which they will need to perform to build new
PCs, and I have volunteered to ask on their behalf here..
As far as they can tell, there is no such an installation option that
tells to install
On 11/4/2013 11:22 AM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
Hello All,
I am trying to help my site's Systems team to straighten up CYGWIN
installation process, which they will need to perform to build new
PCs, and I have volunteered to ask on their behalf here..
As far as they can tell,
Though I haven't experimented with this myself, I'd recommend looking at
using setup*.exe on the command line and listing the packages to install
there.
Thanks. But I P.S.'d about that option as undesirable -- as it requires to
maintain quite a long list of packages, all listed
On 11/4/2013 12:22 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
Though I haven't experimented with this myself, I'd recommend looking at
using setup*.exe on the command line and listing the packages to install
there.
Thanks. But I P.S.'d about that option as undesirable -- as it requires
Just make a list from that as part of your install script.
That is the problem, right there. I counted some 150 directories,
many of which contain 10+ packages, easily. A manageable install
command would have looked like setup.exe -L directory -a to
get and install everything it could have
On 2013-11-04 19:03, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
Just make a list from that as part of your install script.
That is the problem, right there. I counted some 150 directories,
many of which contain 10+ packages, easily. A manageable install
command would have looked like
I have an install script for Cygwin. It's not offline
Thanks for the suggestion. My Systems team need to install from scratch
on bare boxes, from only an image DVD (which contained all the requisites of
the future machine, including CYGWIN's setup and the downloaded directory,
as I previously
On Mon, Nov 04, 2013 at 06:27:48PM +, Lavrentiev, Anton (NIH/NLM/NCBI) [C]
wrote:
I have an install script for Cygwin. It's not offline
Thanks for the suggestion. My Systems team need to install from scratch
on bare boxes, from only an image DVD (which contained all the requisites of
the
On 11/4/2013 1:03 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
Just make a list from that as part of your install script.
That is the problem, right there. I counted some 150 directories,
many of which contain 10+ packages, easily. A manageable install
command would have looked like
Il 11/4/2013 7:03 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] ha scritto:
Just make a list from that as part of your install script.
That is the problem, right there. I counted some 150 directories,
many of which contain 10+ packages, easily. A manageable install
command would have looked like
Are you saying this won't work?
Or do you just not like it?
A little bit of both, actually. Windows CMD.EXE has an 8K limit on the command
line
length, AFAICT. Even if that was not exceeded first time the package list
was created, it may easily get there on a complete re-run of the install
Alternatively, you can grab the sources for setup and add an option
to do what you want the way you want it.
Well, that's a trivial option with open source, of course. But also
it means to maintain a branch of our own setup.exe, which is the
least favorable of all.
Anton Lavrentiev
Contractor
On 11/4/2013 2:04 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
Are you saying this won't work?
Or do you just not like it?
A little bit of both, actually. Windows CMD.EXE has an 8K limit on the command
line
length, AFAICT. Even if that was not exceeded first time the package list
was
On 11/4/2013 2:11 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
Alternatively, you can grab the sources for setup and add an option
to do what you want the way you want it.
Well, that's a trivial option with open source, of course. But also
it means to maintain a branch of our own
genini --recursive x86 x86/setup.ini
That's an interesting piece of information, thanks!
Where can I get genini or upset from?
Anton Lavrentiev
Contractor NIH/NLM/NCBI
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
Lavrentiev, Anton (NIH/NLM/NCBI) [C] writes:
As far as they can tell, there is no such an installation option that
tells to install everything from the download directory. What they
do is that they run setup.exe to manually check everything from the available
packages that they want to have
On Mon, Nov 04, 2013 at 07:11:33PM +, Lavrentiev, Anton (NIH/NLM/NCBI) [C]
wrote:
Alternatively, you can grab the sources for setup and add an option
to do what you want the way you want it.
Well, that's a trivial option with open source, of course. But also
it means to maintain a branch
Lavrentiev, Anton (NIH/NLM/NCBI) [C] writes:
I have an install script for Cygwin. It's not offline
Thanks for the suggestion. My Systems team need to install from scratch
on bare boxes, from only an image DVD (which contained all the requisites of
the future machine, including CYGWIN's setup
Lavrentiev, Anton (NIH/NLM/NCBI) [C] writes:
Alternatively, you can grab the sources for setup and add an option
to do what you want the way you want it.
Well, that's a trivial option with open source, of course. But also
it means to maintain a branch of our own setup.exe, which is the
you're adding additional requirements
Rather revealing them...
The procedure is still to grab the current setup, make package selection,
download with satisfying the dependencies, then install on a bunch of
boxes in the batch mode, unattended.
When a new set of machines is to be built, repeat
Lavrentiev, Anton (NIH/NLM/NCBI) [C] sent the following at Monday, November 04,
2013 1:28 PM
Thanks for the suggestion. My Systems team need to install from
scratch on bare boxes, from only an image DVD (which contained all the
requisites of the future machine, including CYGWIN's setup and the
Il 11/4/2013 8:27 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] ha scritto:
genini --recursive x86 x86/setup.ini
That's an interesting piece of information, thanks!
Where can I get genini or upset from?
Anton Lavrentiev
Contractor NIH/NLM/NCBI
genini:
On Mon, Nov 04, 2013 at 08:13:41PM +, Buchbinder, Barry (NIH/NIAID) [E]
wrote:
Lavrentiev, Anton (NIH/NLM/NCBI) [C] sent the following at Monday, November
04, 2013 1:28 PM
Thanks for the suggestion. My Systems team need to install from
scratch on bare boxes, from only an image DVD (which
25 matches
Mail list logo
