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 Date: Mon, 26 Nov 2001 23:57:32 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: upset and setup.ini change for the next version Message-ID: <20011127045732.GA16578@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <078501c173e4$9dd60070$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <078501c173e4$9dd60070$0200a8c0@lifelesswks> User-Agent: Mutt/1.3.23.1i On Fri, Nov 23, 2001 at 04:49:17PM +1100, Robert Collins wrote: >I've nearly completed the code that will do different requires: clauses >per version of a package. > >The reason is to allow new dependencies to be introduced with a new >version of a package, but not affect folk who don't upgrade the package. >It's also a precursor to embedded metadata. > >However, setup.ini now needs a requires line statement for each >version - ie >[Prev] >Requires: >.. > >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. cgf