<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pkgsrc/devel/p5-PatchReader, branch pkgsrc_2004Q4</title>
<subtitle>[no description]</subtitle>
<id>https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2004Q4</id>
<link rel='self' href='https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2004Q4'/>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/'/>
<updated>2004-12-20T11:30:55Z</updated>
<entry>
<title>since perl is now built with threads on most platforms, the perl archlib</title>
<updated>2004-12-20T11:30:55Z</updated>
<author>
<name>grant</name>
<email>grant</email>
</author>
<published>2004-12-20T11:30:55Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=17843af598da0d77ccfd28ea07f244a331890253'/>
<id>urn:sha1:17843af598da0d77ccfd28ea07f244a331890253</id>
<content type='text'>
module directory has changed (eg. "darwin-2level" vs.
"darwin-thread-multi-2level").

binary packages of perl modules need to be distinguishable between
being built against threaded perl and unthreaded perl, so bump the
PKGREVISION of all perl module packages and introduce
BUILDLINK_RECOMMENDED for perl as perl&gt;=5.8.5nb5 so the correct
dependencies are registered and the binary packages are distinct.

addresses PR pkg/28619 from H. Todd Fujinaka.
</content>
</entry>
<entry>
<title>PatchReader is a set of utilities for reading in, transforming, and doing</title>
<updated>2004-11-03T20:40:43Z</updated>
<author>
<name>adrianp</name>
<email>adrianp</email>
</author>
<published>2004-11-03T20:40:43Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=c99c2bb12004d6ab05e6dae1b8044c6e4183f6a2'/>
<id>urn:sha1:c99c2bb12004d6ab05e6dae1b8044c6e4183f6a2</id>
<content type='text'>
various other things with a patch.  It basically allows you to create a chain of
readers that can read a patch, remove files from a patch, add CVS context, fix
up the patch root according to CVS, and output the patch as raw unified or
through a template processor (used in some places to output a patch as HTML).
</content>
</entry>
</feed>
