cygport development moved from CVS to SVN some time ago, but setup.html
still points to ViewCVS.
OK to apply?
Yaakov
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 @@
</li>
</ul>
<h3>Method Three: cygport</h3>
- <p>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 <tt>cygport</tt> <a
href="http://cygwin-ports.cvs.sourceforge.net/*checkout*/cygwin-ports/cygport/README";>README</a>
explains a number of these problems.</p>
+ <p>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 <tt>cygport</tt> <a
href="http://cygwin-ports.svn.sourceforge.net/viewvc/cygwin-ports/cygport/trunk/README";>README</a>
explains a number of these problems.</p>
<p>The <tt>cygport</tt> 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
<tt>cygport</tt> consult the documentation and sample port files.</p>
<p>Source packages created with <tt>cygport</tt> have a similar
structure to those created with method two, except that they contain a
'<tt>boffo-1.0-1.cygport</tt>' file in place of the '<tt>boffo-1.0-1.sh</tt>'
script. The binary package is built by running '<tt>cygport boffo-1.0-1
all</tt>' instead of '<tt>./boffo-1.0-1.sh all</tt>', and so on for
<tt>prep</tt>, <tt>compile</tt>, <tt>package</tt>, <tt>finish</tt>, etc.</p>
<h2><a id="postinstall" name="postinstall">Creating a package
postinstall script</a></h2>
