Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <053201c14d89$6c909ec0$01000001@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Peter Buckley" <peter DOT buckley AT cportcorp DOT com>, "C" <C AT Gryning DOT com>
Cc: <cygwin AT cygwin DOT com>
References: <001701c14cb9$cc6d4b20$821c10ac AT odin> <3BBC9149 DOT 6B1443B0 AT cportcorp DOT com>
Subject: Re: offering a patch- was [Setup feature query/suggestion!]
Date: Fri, 5 Oct 2001 20:35:11 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400

----- Original Message -----
From: "Peter Buckley" <peter DOT buckley AT cportcorp DOT com>
> Rest of the list-
>
> Is this something that would be appropriate for
> setup.exe to do, or should it be a separate package?

Thats really up to whoever puts the effort in.

> Should it be a gui, or a command line thing?

Why force a choice? do both.

> I'm sure
> I could write a bash script or makefile to do this.
> Are there those on the list who would help me out by
> providing suggestions on the logic that I should use?
>
> I can envision a command like-
>
> apt-get clean /cygdrive/c/cygwin
>
> And the script would look in /cygdrive/c/cygwin
> for a "latest" and "contrib" directory, and then
> go through each package and rm the old ones. But
> rather than compare modification times or version
> numbers in the filenames, is there a sure way to
> make sure we are only removing the packages that are
> older than what is installed- maybe parsing through
> cygcheck output?

If I can offer a couple of observations:
1) There is currently no persistent storage of the install archive
directory. A patch to cygwin to make /var/cache/setup (for example) a
symlink to the location the package cache is in would achieve this in a
simple fashion.
2) The logic to parse /etc/setup.db is already present in setup.exe. So
it would be easier IMO to build a couple of options - say
"remove all files not listed in the current setup.ini" and
"remove all files that have a more recent version installed" - via
setup.exe than
to reinvent that logic (and keep it updated as setup.exe changes).

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/