Index: setup.html =================================================================== RCS file: /cvs/cygwin/htdocs/setup.html,v retrieving revision 1.114 diff -u -r1.114 setup.html --- setup.html 2 Jul 2009 18:18:02 -0000 1.114 +++ setup.html 25 Aug 2009 02:32:40 -0000 @@ -466,7 +466,7 @@

Method Three: cygport

-

The technique of method two became popular to many maintainers, however it suffers from a number of drawbacks when applied on a wide scale. The cygport README explains a number of these problems.

+

The technique of method two became popular to many maintainers, however it suffers from a number of drawbacks when applied on a wide scale. The cygport README explains a number of these problems.

The cygport framework is a response to these issues, and borrows concepts from the Gentoo portage system. It separates the g-b-s into a small file containing the package-specific parts and moves the main script infrastructure into shared files. For more information on using cygport consult the documentation and sample port files.

Source packages created with cygport have a similar structure to those created with method two, except that they contain a 'boffo-1.0-1.cygport' file in place of the 'boffo-1.0-1.sh' script. The binary package is built by running 'cygport boffo-1.0-1 all' instead of './boffo-1.0-1.sh all', and so on for prep, compile, package, finish, etc.

Creating a package postinstall script