Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3EDD405C.2070905@erdfelt.net> Date: Tue, 03 Jun 2003 20:42:04 -0400 From: Joakim Erdfelt User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Looking for Package Donation HOW-TO Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I'm attempting to find a HOW-TO on donating to the cygwin project. Not having much luck tho. I'd like to know what it takes to ... a) update an existing package (fvwm for example. 2.4.7 is current in cygwin, but 2.4.16 is officially the current version). * I'd take on the role of maintainer, but only as far as taking what is recently released and making it compile/install in cygwin, I would leave the bug fixing for the real package maintainers. I'm a high intermediate skill level C/C++ programmer with little to no experience in threads, X11, etc... I am however a great Java developer. but that's useless here. ;-) b) creating a new package for submittal and approval. * I have a working nethack 3.4.0 for example. I think if we have vim and emacs, we _need_ nethack too. ;-) c) what the policy is on 'add-ons' to packages. things like mod_* for apache, or fvwm-themes scripts. Any help, pointers, examples, *DOCS*, etc... would be appreciated. /* joakim */ -- 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/