Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com content-class: urn:content-classes:message Subject: RE: setup 2.194.2.21: Questions about the "per-mirror directories" feature MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 27 Mar 2002 02:29:45 +1100 Message-ID: X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Alexei Lioubimov" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g2QFUVG13146 > -----Original Message----- > From: Alexei Lioubimov [mailto:e-complex AT mtu-net DOT ru] > Sent: Wednesday, March 27, 2002 2:29 AM > To: cygwin AT cygwin DOT com > Subject: setup 2.194.2.21: Questions about the "per-mirror > directories" feature > > > Hello, > I have few questions about the new per-mirror approach of setup: > > 1) What are the advantages, how to make use of them? It's part of allowing federated installation sites - like apt-get or rpmfind. In the mirrors list just add a new mirror by typing it in the box, or select multiple mirrors via ctrl-click or shift-click. > 2) Is it possible to delete old versions (downloaded by old > setup) of the already updated (by new setup) packages? (I > mean, that old versions are still in .../latest & .../contrib > and new ones are in .../some_mirror_site_directory/latest) Up to you. Setup will use everything it can find under the directory you tell it.. > 3) When will be updated the "Cygwin package contributors > guide"? I've been using setup for installing some local stuff > (gtk+ etc) and now i'm not sure about the details - naming > convention, storage, setup.hint & setup.ini syntax and so on... It is up to date! http://www.cygwin.com/setup.html. Cheers, 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/