* Running Cygwin's "setup.exe" on a new computer
@ 2015-09-01 12:50 Dr Rainer Woitok
2015-09-01 13:57 ` Marco Atzeri
2015-09-02 7:17 ` Achim Gratz
0 siblings, 2 replies; 6+ messages in thread
From: Dr Rainer Woitok @ 2015-09-01 12:50 UTC (permalink / raw)
To: cygwin
Greetings,
having installed Cygwin on my old computer it's now time to move to new
hardware. Are there any Cygwin configuration or status files I could
copy from the old box to the new one which would cause "setup.exe" on
the new machine to automatically install the same packages as on the old
computer (except for version changes or new dependencies)?
One minor additional problem perhaps: the old box is 32 bit, while the
new one is 64 bit.
Any help welcome.
Sincerely,
Rainer
PS: Please also reply by personal mail as I am not subscribed to the
Cygwin mailing list.
--
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Running Cygwin's "setup.exe" on a new computer
2015-09-01 12:50 Running Cygwin's "setup.exe" on a new computer Dr Rainer Woitok
@ 2015-09-01 13:57 ` Marco Atzeri
2015-09-02 10:54 ` Dr Rainer Woitok
2015-09-02 7:17 ` Achim Gratz
1 sibling, 1 reply; 6+ messages in thread
From: Marco Atzeri @ 2015-09-01 13:57 UTC (permalink / raw)
To: cygwin, Rainer.Woitok
On 01/09/2015 14:50, Dr Rainer Woitok wrote:
> Greetings,
>
> having installed Cygwin on my old computer it's now time to move to new
> hardware. Are there any Cygwin configuration or status files I could
> copy from the old box to the new one which would cause "setup.exe" on
> the new machine to automatically install the same packages as on the old
> computer (except for version changes or new dependencies)?
>
> One minor additional problem perhaps: the old box is 32 bit, while the
> new one is 64 bit.
>
> Any help welcome.
>
> Sincerely,
> Rainer
>
> PS: Please also reply by personal mail as I am not subscribed to the
> Cygwin mailing list.
>
something like this should work
$ cygcheck -cd | awk 'BEGIN{printf("setup-x86_64.exe ")} {if (NR>2) {
printf ("-P " $1 " ") }} END { printf ("\r\n pause ")}' >
cyg-install-x86_64.bat
$ chmod +x cyg-install-x86_64.bat
Of course copy the "cyg-install-x86_64.bat" where the
"setup-x86_64.exe" is on the new computer.
Regards
Marco
--
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
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Running Cygwin's "setup.exe" on a new computer
2015-09-01 13:57 ` Marco Atzeri
@ 2015-09-02 10:54 ` Dr Rainer Woitok
2015-09-02 12:06 ` Marco Atzeri
0 siblings, 1 reply; 6+ messages in thread
From: Dr Rainer Woitok @ 2015-09-02 10:54 UTC (permalink / raw)
To: Marco Atzeri; +Cc: cygwin
Marco,
On Tuesday, 2015-09-01 15:57:03 +0200, you wrote:
> ...
> $ cygcheck -cd | awk 'BEGIN{printf("setup-x86_64.exe ")} {if (NR>2) {
> printf ("-P " $1 " ") }} END { printf ("\r\n pause ")}' > cyg-install-x86_64.bat
Even if I slightly compress the command line created that way by using a
single "-P" option followed by the string of comma separated package
names, I end up with a command line consisting of some 16700 characters!
I'm not at all sure how Windows and/or "setup-x86*.exe" would react to
that.
Besides, since "cygcheck" apparently finds the relevant information in
some file, and "setup-x86*.exe" apparently finds the relevant informat-
ion in some file, too, it would perhaps be way easier to just provide
the correct file in the correct location on the new machine.
Any ideas along these lines, anybody?
Sincerely,
Rainer
--
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
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Running Cygwin's "setup.exe" on a new computer
2015-09-02 10:54 ` Dr Rainer Woitok
@ 2015-09-02 12:06 ` Marco Atzeri
2015-09-03 14:24 ` Warren Young
0 siblings, 1 reply; 6+ messages in thread
From: Marco Atzeri @ 2015-09-02 12:06 UTC (permalink / raw)
To: Dr Rainer Woitok; +Cc: cygwin
On 02/09/2015 12:53, Dr Rainer Woitok wrote:
> Marco,
>
> On Tuesday, 2015-09-01 15:57:03 +0200, you wrote:
>
>> ...
>> $ cygcheck -cd | awk 'BEGIN{printf("setup-x86_64.exe ")} {if (NR>2) {
>> printf ("-P " $1 " ") }} END { printf ("\r\n pause ")}' > cyg-install-x86_64.bat
>
> Even if I slightly compress the command line created that way by using a
> single "-P" option followed by the string of comma separated package
> names, I end up with a command line consisting of some 16700 characters!
> I'm not at all sure how Windows and/or "setup-x86*.exe" would react to
> that.
My W7 64bit had no complain for 23004 byte line
;-)
> Besides, since "cygcheck" apparently finds the relevant information in
> some file, and "setup-x86*.exe" apparently finds the relevant informat-
> ion in some file, too, it would perhaps be way easier to just provide
> the correct file in the correct location on the new machine.
>
> Any ideas along these lines, anybody?
https://cygwin.com/ml/cygwin/2015-09/msg00023.html
>
> Sincerely,
> Rainer
>
--
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Running Cygwin's "setup.exe" on a new computer
2015-09-01 12:50 Running Cygwin's "setup.exe" on a new computer Dr Rainer Woitok
2015-09-01 13:57 ` Marco Atzeri
@ 2015-09-02 7:17 ` Achim Gratz
1 sibling, 0 replies; 6+ messages in thread
From: Achim Gratz @ 2015-09-02 7:17 UTC (permalink / raw)
To: cygwin
> having installed Cygwin on my old computer it's now time to move to new
> hardware. Are there any Cygwin configuration or status files I could
> copy from the old box to the new one which would cause "setup.exe" on
> the new machine to automatically install the same packages as on the old
> computer (except for version changes or new dependencies)?
You can drop /etc/setup/installed.db into the new installation directory and
make them all "outdated":
sed -i.bak -re 's/^(.+) .+ 0$/\1 \1-0-0.tar.bz 0/' /etc/setup/installed.db
Running setup on this will then "update" all these packages. It will
complain about the missing package lst.gz files of course, but you can
ignore that.
> One minor additional problem perhaps: the old box is 32 bit, while the
> new one is 64 bit.
There's only a handful of packages left where that makes a difference.
> PS: Please also reply by personal mail as I am not subscribed to the
> Cygwin mailing list.
No can do via Gmane and the list is set up specificaly to prevent this
anyway. In general, if you do indeed care about the answers you can always
check Gmane or the mailing list archives.
Regards,
Achim.
--
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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2015-09-03 14:24 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-09-01 12:50 Running Cygwin's "setup.exe" on a new computer Dr Rainer Woitok
2015-09-01 13:57 ` Marco Atzeri
2015-09-02 10:54 ` Dr Rainer Woitok
2015-09-02 12:06 ` Marco Atzeri
2015-09-03 14:24 ` Warren Young
2015-09-02 7:17 ` Achim Gratz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).