From 9eba97c0d5d723ce151b38d4bc78bd6fe097336c Mon Sep 17 00:00:00 2001 From: Joshua Daniel Franklin Date: Sat, 26 Mar 2005 04:01:52 +0000 Subject: [PATCH] Mention generic-build-script in packaging FAQ --- winsup/doc/ChangeLog | 5 +++++ winsup/doc/how-programming.texinfo | 28 ++++++++++++++++------------ 2 files changed, 21 insertions(+), 12 deletions(-) diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog index 6d10c1bec..3edb971d0 100644 --- a/winsup/doc/ChangeLog +++ b/winsup/doc/ChangeLog @@ -1,3 +1,8 @@ +2005-03-25 Joshua Daniel Franklin + + * how-programming.texinfo: Mention generic-build-script in + packaging FAQ. + 2005-03-19 Joshua Daniel Franklin * how-programming.texinfo: Remove incorrect libm.a note. diff --git a/winsup/doc/how-programming.texinfo b/winsup/doc/how-programming.texinfo index b43b96e8a..f8a6150e3 100644 --- a/winsup/doc/how-programming.texinfo +++ b/winsup/doc/how-programming.texinfo @@ -2,22 +2,26 @@ @subsection How do I contribute a package? -If you are willing to be a package maintainer, great. We urgently need +If you are willing to be a package maintainer, great! We urgently need volunteers to prepare and maintain packages, because the priority of the Cygwin Team is Cygwin itself. -The Cygwin Package Contributor's Guide is at -@file{http://cygwin.com/setup.html}, which details everything you need -to know about being a package maintainer. Use the cygwin-apps mailing -list (start at @file{http://cygwin.com/lists.html}) for -questions about package maintenance, @emph{after} searching and browsing the -cygwin-apps list archives, of course. Charles Wilson posted a short -recipe of what is involved, using texinfo as an example, available at -@file{http://cygwin.com/ml/cygwin-apps/2000-11/msg00055.html}. This -should give you an idea of what is required. +The Cygwin Package Contributor's Guide at +@file{http://cygwin.com/setup.html} details everything you need to know +about being a package maintainer. The quickest way to get started is to +read the @emph{Initial packaging procedure, script-based} section on +that page. The @samp{generic-build-script} found there works well for +most packages. -You should announce your intentions to the general cygwin list, in case -others were thinking the same thing. +For questions about package maintenance, use the cygwin-apps mailing +list (start at @file{http://cygwin.com/lists.html}) @emph{after} +searching and browsing the cygwin-apps list archives, of course. Be +sure to look at the @emph{Submitting a package} checklist at +@file{http://cygwin.com/setup.html} before sending an ITP (Intent To +Package) email to cygwin-apps. + +You should also announce your intentions to the general cygwin list, in +case others were thinking the same thing. @subsection How do I contribute to Cygwin?