Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID: <3B4661CC.5080804@ece.gatech.edu>
Date: Fri, 06 Jul 2001 21:11:40 -0400
From: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.1) Gecko/20010607 Netscape6/6.1b1
X-Accept-Language: en-us
MIME-Version: 1.0
To: Dario Alcocer <alcocer AT helixdigital DOT com>
CC: cygwin-apps AT cygwin DOT com
Subject: Re: Package maintainer release procedures
References: <15174 DOT 18698 DOT 346785 DOT 618387 AT coyote DOT priv DOT helixdigital DOT com>	<3B465441 DOT C8695619 AT t-online DOT de> <15174 DOT 22196 DOT 669125 DOT 221517 AT coyote DOT priv DOT helixdigital DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Dario Alcocer wrote:

>>>>>>"Jerome" == Jerome BENOIT <520066587150-0001 AT t-online DOT de> writes:
>>>>>>
> 
>     Jerome> Bonjour:
> 
>     Jerome> "How do I contribute a package" link in the FAQ:
>     Jerome> http://cygwin.com/faq/faq_4.html#SEC76
> 
>     Jerome> Follow the link and you shall get what you want.
> 
> Hmm, well, the link talks about *packaging*, not package submision :-)
> I already read the link from the FAQ you're refering to; I've packaged
> up the binary and source tar balls following exactly this procedure.
> Now, what I need to know is how to *upload* (not package) these files
> to the mirrors.


There are two ways:

1) some contributors have login accounts on sourceware and upload new 
packages themselves.  The decision to grant such access is solely the 
responsibility of the Red Hat management folks.

2) I have also seen cgf specifically request that a contributor mail the 
files to him, and he has placed them on sourceware.  (Don't just spam 
him with unsolicited tarballs, though -- wait for a request)


> Regarding the anouncement, I was planning on just sending to
> cygwin-announce (and letting the moderator approve/reject my
> announcement) but I wanted to know what the "approved" procedure was
> before I did anything.


That's the typical method -- just send your announcement to 
cygwin-announce, and the moderator will handle it from there. Use a 
recent announcement as a model for the "boilerplate" stuff.

As far as composition, some contributors are fairly sparse, leaving 
documentation to the README files; others (like me) prefer to put lots 
of info in the announcement to cut down on mailing list traffic from 
those who will read the ann. but not the README.  (I think "my side" has 
been winning points lately vis a vis the "cron" package...)

--Chuck