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 Message-ID: <3C204477.8050904@ece.gatech.edu> Date: Wed, 19 Dec 2001 02:40:39 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: Gareth Pearce CC: cygwin-apps AT cygwin DOT com Subject: Re: Restructuring gettext References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Gareth Pearce wrote: > I am going to release nano 1.0.7 after christmas (on holidays right now > or I would release it tommorow) which fixes a few things including > locale being installed in the wrong directory - it also compiles > completely without modification straight from the box - got my lil > problems fixed at the source :) > > anyway ... until 1.1.5 or so (which should be my next release after > 1.0.7 I think) and both versions are recompiled to depend on libintl1 I > assume my setup.hint will have to depend on Both libintl and libintl1 > correct? Ummm... nano-1.0.6-1 depends on libintl nano-1.0.7 will depend on libintl1 Since we don't yet have per-version dependencies, it isn't clear what setup.hint should say during the "transition" period, when prev depends on libintl and curr depends on libintl1. I'm planning on specifying only the most recent -- folks who have already installed the old version of package nano will already have the old version of the the libintl library. > or should I do something else? It's up to you, I guess. --Chuck