Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Message-ID: <003501c17707$4cbb1510$0200a8c0@lifelesswks> From: "Robert Collins" To: References: <078501c173e4$9dd60070$0200a8c0 AT lifelesswks> <20011127045732 DOT GA16578 AT redhat DOT com> Subject: Re: upset and setup.ini change for the next version Date: Tue, 27 Nov 2001 16:49:36 +1100 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 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 27 Nov 2001 05:49:32.0443 (UTC) FILETIME=[497C16B0:01C17707] ----- Original Message ----- From: "Christopher Faylor" > >Chris, can upset handle this now? > > Sorry it took so long to answer this. > > The answer, of course, is no. If upset was to handle this now it would > output confusing and potentially incorrect setup.ini files. > > I'm not sure how you're going to get this information into setup.hint, since > the current syntax doesn't allow this. Perhaps we can start by having upset spit out the requires line for each [prev/curr] entry. This should suffice until I've got the embedded metadata sorted, at which point the setup.hint syntax can start getting smaller, and only contain the stability information, which cannot be contained within the tarballs. Rob