MIME-Version: 1.0
In-Reply-To: <4B32D9A4.907@columbus.rr.com>
References: <4B32D9A4.907@columbus.rr.com>
Date: Thu, 24 Dec 2009 07:43:07 +0000
Message-ID: <416096c60912232343q5ec6c8a3tf49007e5704d616b@mail.gmail.com>
Subject: Re: A question about setup.exe
From: Andy Koppe <andy.koppe@gmail.com>
To: pmcferrin@columbus.rr.com, cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

2009/12/24 Paul McFerrin:
> I did the upgrade to 1.7.1-1 without any problems. =C2=A0During the remai=
nder of
> the day, I accidentally blew away my installation of 1.7.1-1. =C2=A0I res=
tored my
> installation from a backup several days old (1.7.0-65). =C2=A0Now I'm try=
ing to
> upgrade again.
>
> Now the questions I have are:
> When I run setup again, it downloads/installes everything in under a minu=
te
> instead of the hour previously.

It wouldn't need to download the packages again, because they should
still be stored in setup.exe's local package directory. So it only
needs to do the install.

> How can I "force" all of my installed
> packages obsolete to force a reload?

If the backup and restore went correctly, you shouldn't need to,
because the install state of all packages is stored in the cygwin
directory, in /etc/setup. You can see which packages are going to be
upgraded by switching to the "Partial" view on setup.exe's package
selection screen.

Andy

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