X-Spam-Check-By: sourceware.org Message-ID: <467B2CCE.8030005@math.cornell.edu> Date: Thu, 21 Jun 2007 21:58:38 -0400 From: Ken Brown User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: emacs 22.1? References: <20070618084646.GK4179@calimero.vinschen.de> <20070618130035.GN4179@calimero.vinschen.de> <1182194212.467427@alpaka.in-berlin.de> <20070618204746.GA1813@ednor> <46781F52.7BDF4B@dessent.net> <1182451702.807043@alpaka.in-berlin.de> <467AE8BF.5B11A928@dessent.net> In-Reply-To: <467AE8BF.5B11A928@dessent.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 6/21/2007 5:08 PM, Brian Dessent wrote: > Steffen Sledz wrote: > >> Hmmm? I'm not sure if this is a practical solution because the old >> emacs-leim package is just obsolete, if a new emacs package is >> installed. How can i describe this inter-package dependency? > > There's no way to express any version specific requirements. Once the > old emacs package gets demoted to [prev], it becomes a second class > citizen. In order to use it the user would have to know to set 'emacs' > to [prev] as well as 'emacs-leim' to [prev] as well (you can state this > in the release announcement.) Or in other words, upgrading to the v22 > emacs package should have the effect of also uninstalling v21 > emacs-leim, which is accomplished by installing the new [curr] of both > packages. Here I'm assuming that having a v22 emacs and a v21 > emacs-leim both installed at the same time causes breakage. I don't think it causes breakage. Emacs-leim is installed in a version-specific directory (such as /usr/share/emacs/21.3.50/leim). V22 emacs won't even look there. Ken -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/