X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <20080405095403.2168@blackhawk>
Date: Sat, 05 Apr 2008 09:54:03 +0900
From: wynfield AT gmail DOT com
To: <cygwin AT cygwin DOT com>
cc: 
Subject: gettext latest vers. 0.17
X-Mailer: MH-E 8.0.3+cvs; GNU Mailutils 1.9.90; GNU Emacs 23.0.50
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com


Just as the person below noted that the latest version of gettext, 0.17 was needed, I found myself also needing it.  I expect that more and more newer versions and updates will be requiring it.

http://cygwin.com/ml/cygwin/2008-03/msg00220.html

The current cygwin gettext package is over two years old.  The below cygwin archive gives an explanation for this.

http://www.cygwin.com/ml/cygwin/2008-02/msg00359.html

My question is the usage of "cygport" really required to be used.  I certainly feel that it should not be required and it has certainly appeared to hamper a lot of progress in maintenance and updates of existing packages.

It is a tool, best know by its developer, but it is merely a tool and should not be a required one.  Cygwin already has a specification for packages, the only requirement should be that a package meets that specification, not how it was accomplished.

It would be great to allow that freedom and then we can get a latest update of gettext and all would be happy.

This is my understanding.   Please comment on the "required use" of cygport.  And who said it is required and why.


Cheers,



--
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/