X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW,TW_YG
X-Spam-Check-By: sourceware.org
Message-ID: <4E84B4AE.40606@cwilson.fastmail.fm>
Date: Thu, 29 Sep 2011 14:10:54 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
Reply-To: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:7.0) Gecko/20110922 Thunderbird/7.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: libunistring?
References: <4E8474FF DOT 7010309 AT xs4all DOT nl> <4E847914 DOT 70107 AT gmail DOT com> <4E84892F DOT 9060208 AT xs4all DOT nl>
In-Reply-To: <4E84892F.9060208@xs4all.nl>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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

On 9/29/2011 11:05 AM, Erwin Waterlander wrote:
> Somebody already created Cygwin packages. See the URL at fd0.x0.to. But
> I don't see who's behind it.

The included readme in the package says this person:
http://d.hatena.ne.jp/fd0/
But I don't speak/read japanese...

FWIW, the -src package uses cygport and provides a minimal src patch
(disables using the .rc file and adding properties to the dll), along
with a cygwin patch providing a readme and setup.hint. (hint lists
cygwin as a require: but this is no longer recommended practice).


We can't just grab some cygwin package off a website and stick it in the
distribution. We need an actual maintainer, who is a member of this
community (at least, subscribed to the cygwin mailing list), who commits
to supporting the package, and to ITP it on cygwin-apps. Then there's
the whole GTG evaluation and voting process (or documentation that the
package is provide by (at least one) major linux distro).

It's fine with me if that volunteer wants to /start/ with a 3rd party
cygport script and patchset, but the volunteer needs to "take ownership"
of it going forward.

--
Chuck




--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple