<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pkgsrc/databases/p5-Search-QueryParser-SQL/Makefile, branch pkgsrc_2011Q1</title>
<subtitle>[no description]</subtitle>
<id>https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2011Q1</id>
<link rel='self' href='https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2011Q1'/>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/'/>
<updated>2010-08-21T16:32:42Z</updated>
<entry>
<title>Bump the PKGREVISION for all packages which depend directly on perl,</title>
<updated>2010-08-21T16:32:42Z</updated>
<author>
<name>seb</name>
<email>seb</email>
</author>
<published>2010-08-21T16:32:42Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=2071bb5c54efeb5a369d623a737c040e30ff5a84'/>
<id>urn:sha1:2071bb5c54efeb5a369d623a737c040e30ff5a84</id>
<content type='text'>
to trigger/signal a rebuild for the transition 5.10.1 -&gt; 5.12.1.

The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.

sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
</content>
</entry>
<entry>
<title>Updating package databases/p5-Search-QueryParser-SQL from 0.007 to 0.008</title>
<updated>2009-08-19T20:36:16Z</updated>
<author>
<name>sno</name>
<email>sno</email>
</author>
<published>2009-08-19T20:36:16Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=305f7929face68da7784ab61c78147a2c1b25f05'/>
<id>urn:sha1:305f7929face68da7784ab61c78147a2c1b25f05</id>
<content type='text'>
pkgsrc changes:
  - Adding license
  - Adjusting dependencies
  - Using "correct" module type

Upstream changes:
0.008   18 Aug 2009
        * add tests and support for fuzzy int-types
        * refactor to include an explicit Column class to allow for more
          granular control of sql building. Thanks to John Maslanik for the prompting
          that led to this idea.
</content>
</entry>
<entry>
<title>Update from version 0.005nb1 to 0.007.</title>
<updated>2008-12-20T16:38:22Z</updated>
<author>
<name>he</name>
<email>he</email>
</author>
<published>2008-12-20T16:38:22Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=305160101bb44560f3b36db13781961a0822ba66'/>
<id>urn:sha1:305160101bb44560f3b36db13781961a0822ba66</id>
<content type='text'>
Upstream changes:

0.007   4 Dec 2008
        * add fuzzify2 feature

0.006   22 Nov 2008
        * fix overload bug for Test::More 0.86
</content>
</entry>
<entry>
<title>Bump the PKGREVISION for all packages which depend directly on perl,</title>
<updated>2008-10-19T19:17:40Z</updated>
<author>
<name>he</name>
<email>he</email>
</author>
<published>2008-10-19T19:17:40Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=5209d3b6614856d771465489fa3399121b800518'/>
<id>urn:sha1:5209d3b6614856d771465489fa3399121b800518</id>
<content type='text'>
to trigger/signal a rebuild for the transition 5.8.8 -&gt; 5.10.0.

The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=...").
</content>
</entry>
<entry>
<title>Import p5-Search-QueryParser-SQL version 0.005.</title>
<updated>2008-10-12T21:55:10Z</updated>
<author>
<name>he</name>
<email>he</email>
</author>
<published>2008-10-12T21:55:10Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=ea0c6ed5007230a65abcd2de3daf1a5c7f903d97'/>
<id>urn:sha1:ea0c6ed5007230a65abcd2de3daf1a5c7f903d97</id>
<content type='text'>
Search::QueryParser::SQL is a subclass of Search::QueryParser.
Chiefly it extends the unparse() method to stringify free-text
search queries as valid SQL WHERE clauses.

The idea is to allow you to treat your database like a free-text
search index, when it really isn't.

</content>
</entry>
</feed>
