Message-ID: <4E8E070C.5000401@xs4all.nl>
Date: Thu, 06 Oct 2011 21:52:44 +0200
From: Erwin Waterlander <waterlan@xs4all.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: libunistring?
References: <4E8474FF.7010309@xs4all.nl> <4E847914.70107@gmail.com> <4E84892F.9060208@xs4all.nl> <4E84B4AE.40606@cwilson.fastmail.fm>
In-Reply-To: <4E84B4AE.40606@cwilson.fastmail.fm>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Charles Wilson schreef, Op 29-9-2011 20:10:
>
>
> 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.
>
> --
>

I started packaging libunistring from scratch. I didn't look at the 
other package. Expect an ITP message on cygwin-apps soon.

best regards,

-- 
Erwin Waterlander


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