Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com content-class: urn:content-classes:message Subject: RE: Setup/prev/curr/test/metapackages/another screen/etc MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 27 Mar 2002 16:11:07 +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: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g2R5D2o27805 > -----Original Message----- > From: Christopher Faylor [mailto:cygwin-apps AT cygwin DOT com] > Sent: Wednesday, March 27, 2002 3:40 PM > It's an interesting idea but I don't like glumping what used > to be prev/curr/test with the concept of packages or meta > packages. You lose some functionality that way. Yes. > I really wish we had never even come up with the concept of > prev/curr/test. Maybe the prev release should be a > completely separate release, ditto test. Yes. This is how I've been suggesting they get managed for a while now. Not to the same extent of separation that debian has, but separate. > test/latest > test/contrib > > curr/latest > curr/contrib > > prev/latest > prev/contrib I think that the file locations are orthogonal to the versions considered 'active' in test/curr/prev. Debian (to use the old example), once had fully separate directories, but changed to be a single directory structure, with separate indexes - and those indexes are ~= setup.ini. Rob