public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: LMH <lmh_users-groups@molconn.com>
To: cygwin@cygwin.com
Subject: Re: offline cygwin install question
Date: Thu, 27 Jun 2013 20:19:00 -0000	[thread overview]
Message-ID: <51CC9DC1.3000309@molconn.com> (raw)
In-Reply-To: <20130627191501.GA5391@ednor.casa.cgf.cx>

> I don't see why.  If the directory is duplicated precisely I don't see
> how it could matter.

What I was referring to here was to just copy the cygwin local package 
directory that contains setup.exe and the http% mirror directories, not 
the directory that contains installed cygwin. When I moved the local 
package directory to a new machine and ran setup.exe with install from 
local directory, there sometimes were problems.

If there was only one http% directory

/http%3a%2f%2fwww.gtlib.gatech.edu%2fpub%2fcygwin%2f
/setup.exe
/setup.log

(meaning all of the cygwin install on the machine where I took the 
setup.exe dir from had been done from the same mirror)

then running setup.exe worked fine and I got a functional cygwin.

If found that if there were several mirror directories,

/http%3a%2f%2fcygutils.fruitbat.org%2fITP%2fmingw-gcc%2f
/http%3a%2f%2fmirror.cs.vt.edu%2fpub%2fcygwin%2fcygwin%2f
/http%3a%2f%2fwww.gtlib.gatech.edu%2fpub%2fcygwin%2f
/setup.exe
/setup.log

then running setup.exe would install only the packages in the last 
mirror used and there would be a number of things missing from the 
install (like the cygwin.dll). I did this before I knew that I could 
just move the entire installed cygwin directory to a different machine.


Regarding this set of instructions,
http://cygwin.com/ml/cygwin/2013-06/msg00657.html

they seem to be a bit more involved than is necessary. My cygwin install 
directory is less than 1GB, so what is the need to use tar? I believe 
that when I last re-installed my current OS, I just copied my cygwin 
folder to a backup drive and then copied it back to C: after my 
re-install. Is there some reason why that is a bad idea?

LMH



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

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

  reply	other threads:[~2013-06-27 20:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27  2:35 LMH
2013-06-27  2:40 ` wynfield
2013-06-27  4:49   ` LMH
2013-06-27  8:32   ` Christopher Faylor
2013-06-27 13:08   ` Buchbinder, Barry (NIH/NIAID) [E]
2013-06-27  8:33 ` Corinna Vinschen
2013-06-27 17:00   ` Christopher Faylor
2013-06-27 18:25     ` LMH
2013-06-27 19:22       ` Christopher Faylor
2013-06-27 20:19         ` LMH [this message]
2013-06-27 20:47           ` Christopher Faylor
2013-06-28 22:05             ` Christopher Faylor
2013-09-08  5:40 R.Penney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51CC9DC1.3000309@molconn.com \
    --to=lmh_users-groups@molconn.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).