Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Sun, 23 Dec 2001 13:43:28 -0500 From: Christopher Faylor To: cygwin-apps@cygwin.com, cygwin@cygwin.com Subject: Re: Setup.exe snapshot Message-ID: <20011223184328.GB21163@redhat.com> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com, cygwin@cygwin.com References: <02b801c18bb1$ad62f360$0200a8c0@lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <02b801c18bb1$ad62f360$0200a8c0@lifelesswks> User-Agent: Mutt/1.3.23.1i On Sun, Dec 23, 2001 at 11:59:33PM +1100, Robert Collins wrote: >* Dependencies will only trigger installation of a package - they won't >force an upgrade of an installed package. (with the caveat that in the >future versioned dependencies may force upgrades). Isn't this what has consistently gotten us into trouble? Why not force an update of a package if a package that depends on it is being upgraded? This seems more intuitive to me. Also, if we have no way to install all packages, then I think this new release should be delayed. We've been promising this for months. If all that we need, however, is for upset to add things to a "Full" category, which can be selected, I can do that. cgf -- 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/