From: Warren Young <wyml@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Installation data under "~/Downloads/cygwin/"
Date: Mon, 04 May 2015 19:47:00 -0000 [thread overview]
Message-ID: <78DCE27F-6CB2-4ECE-9666-39E378A9371D@etr-usa.com> (raw)
In-Reply-To: <21831.43821.807000.397963@woitok.gmail.com>
On May 4, 2015, at 11:23 AM, Dr Rainer Woitok <rainer.woitok@gmail.com> wrote:
>
> On Saturday, 2015-05-02 01:35:37 +0300, you wrote:
>
>> ...
>> You may safely nuke everything that is not your Cygwin installation.
>
> Well, what precisely IS my Cygwin installation? Only the stuff in "C:\
> cygwin\”?
Yes, though I wouldn’t have put it the way Andrey did. I mean, c:\windows is not your Cygwin installation, but you cannot safely nuke it. :)
The real point is that the Cygwin download directory can be safely nuked. Keeping it just speeds reinstallation. If you’re not storing the Cygwin download directory on a NAS or other type of file server for use by multiple computers, you probably don’t need to keep the download directory.
> And how does Cygwin's "setup.exe" know which version of what
> is already installed?
It reads the database stored as /etc/setup/installed.db.
> What are the "setup.ini" files under "C:\Users\Admin\Downloads\
> cygwin\" used for?
Those are databases listing the packages available from the mirror you selected, along with other metadata such as version numbers, dependency info, descriptions, etc. You can open it in a text editor and see all of this.
--
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
prev parent reply other threads:[~2015-05-04 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 11:35 Dr Rainer Woitok
2015-05-01 12:23 ` Marco Atzeri
2015-05-02 8:50 ` Andrey Repin
2015-05-04 17:58 ` Dr Rainer Woitok
2015-05-04 19:47 ` Warren Young [this message]
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=78DCE27F-6CB2-4ECE-9666-39E378A9371D@etr-usa.com \
--to=wyml@etr-usa.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).