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: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Thu, 13 Dec 2001 16:59:26 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: Restructuring gettext Message-ID: <20011213215926.GA20163@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <3C18EBA9 DOT 9030102 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C18EBA9.9030102@ece.gatech.edu> User-Agent: Mutt/1.3.23.1i On Thu, Dec 13, 2001 at 12:55:53PM -0500, Charles Wilson wrote: >However, this means that the new gettext dll is not backward compatible >with packages linked against the old dll The term "glutton for punishment" springs to mind. >How should we handle this sort of thing in the future, when setup.hints >of OTHER packages need to be updated, but the one forcing the change >(me, in this case) is not the maintainer of those other packages? > >Oh yeah: link > http://www.neuro.gatech.edu/users/cwilson/cygutils/testing/gettext/ I think we should consider it the responsibility of the package maintainer to maintain all occurrences of the name of his package. So, it would be within your right to change mutt to accomodate your changes -- as long as you let the mutt maintainer know about this. cgf