X-Spam-Check-By: sourceware.org
Message-ID: <4382BCC2.515350F0@dessent.net>
Date: Mon, 21 Nov 2005 22:37:54 -0800
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Folder ftp%3a%2f%2fftp.sunsite.utk.edu%2fpub%2fcygwin remains  after   install
References: <1132608508 DOT 5513 DOT 11 DOT camel AT math DOT jpl DOT nasa DOT gov> <Pine DOT GSO DOT 4 DOT 63 DOT 0511211717140 DOT 18715 AT slinky DOT cs DOT nyu DOT edu> <4382BA57 DOT 5090107 AT t-online DOT de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Christian Franke wrote:

> Somewhat offtopic and probably FAQ:
> The local package cache fills up with outdated (no longer in setup.ini)
> versions.
> Is there any hidden setup.exe functionality or cleanup script available
> to delete old package files?

There's nothing in setup.exe, but I do remember that someone once posted
a script that does this.  I don't recall the filename but google on the
mailing list archives ought to work.

I prefer to maintain a local rsync repository rather than letting
setup.exe download anything.  If you go this route you can use --delete
to delete stuff no longer on the master site.  You can be pretty
flexible in what you mirror, e.g. --exclude=\*-src.tar\* to skip source
packages (though I don't do this.)

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/