similar to: Re: [Xapian-commits] Changes in xapian/xapian-core/

Displaying 20 results from an estimated 20000 matches similar to: "Re: [Xapian-commits] Changes in xapian/xapian-core/"

2004 May 11
2
Re: [Xapian-commits] Changes in xapian/xapian-applications/queryserver/ xapian/xapian-applications/queryserver/source/
On Tue, May 11, 2004 at 05:41:58PM +0100, Richard Boulton wrote: > * If the queryserver can't parse a query, strip out all special > characters, and then retry. This means that we get some kind of > result even if the query is broken. That's probably a feature worth pushing down into Xapian::QueryParser... Cheers, Olly
2007 Apr 13
1
Re: [Xapian-commits] 8229: trunk/xapian-core/ trunk/xapian-core/api/
olly wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: olly > Revision: 8229 > Date: 2007-04-13 10:18:52 +0100 (Fri, 13 Apr 2007) > > Log message (4 lines): > api/version.cc: Simpler and cleaner fix - the prototypes for the > version functions had moved from xapian/version.h to xapian.h so we > were including the wrong header and not
2007 Apr 23
1
Re: [Xapian-commits] 8351: trunk/xapian-core/ trunk/xapian-core/backends/flint/
olly wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: olly > Revision: 8351 > Date: 2007-04-23 01:44:44 +0100 (Mon, 23 Apr 2007) > > Log message (2 lines): > backends/flint/flint_version.cc: Update the flint format version > since older flint versions can't read compressed tags. Am I correct in assuming that this means that when
2007 Apr 09
1
Re: [Xapian-commits] 8157: trunk/xapian-core/ trunk/xapian-core/backends/flint/ trunk/xapian-core/backends/quartz/
olly wrote: > Log message (6 lines): > backends/flint/flint_database.cc: Delete the corresponding entry > (if any) from doclens in delete_document(). Add assertion to > add_document_() that the corresponding entry in doclens isn't > already set, but in a non-debug build overwrite any existing > entry as that's more likely to be correct. >
2007 Jun 30
1
Re: [Xapian-commits] 9092: trunk/xapian-core/ trunk/xapian-core/api/ trunk/xapian-core/common/ trunk/xapian-core/include/xapian/
olly wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: olly > Revision: 9092 > Date: 2007-06-30 15:16:16 +0100 (Sat, 30 Jun 2007) > > Log message (2 lines): > api/omdocument.cc,common/document.h,include/xapian/document.h: > Add Xapian::Document::get_docid() method. I was thinking that it would probably be useful to have a
2007 Feb 26
1
Re: [Xapian-commits] 7759: trunk/xapian-core/ trunk/xapian-core/tests/harness/
olly wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: olly > Revision: 7759 > Date: 2007-02-26 18:38:13 +0000 (Mon, 26 Feb 2007) > > Log message (3 lines): > tests/harness/backendmanager.cc: Indent with tabs not spaces. Hmm - this space thing is getting silly - I have my editor set to not expand tabs, but spaces crept in because I
2007 Apr 05
1
Re: [Xapian-commits] 8107: trunk/xapian-core/ trunk/xapian-core/backends/
olly wrote: > Log message (7 lines): > backends/database.cc: Database::Internal can't call the > PostingIterator(PostingIterator::Internal*) ctor (at least under > g++ 3.3.5) because it isn't a friend (only class Database is). For the record, Mark just reported this to me under windows so it was a problem there too, but it does work under GCC 4.1. No idea which compiler is
2016 Mar 26
2
PHP bindings fail on Ubuntu for xapian-bindings-1.2.21
Hi Olly and co, On an Ubuntu 15.10, following the docs at https://trac.xapian.org/wiki/FAQ/PHP%20Bindings%20Package When running debuild -e PHP_VERSIONS=5 -us -uc I get (sorry for the French): " dpkg-buildpackage -rfakeroot -D -us -uc dpkg-buildpackage: paquet source xapian-bindings dpkg-buildpackage: version source 1.2.21-2.1 dpkg-buildpackage: distribution source unstable
2016 Mar 26
3
PHP bindings fail on Ubuntu for xapian-bindings-1.2.21
Le 26/03/16 18:04, Olly Betts a ?crit : > On Sat, Mar 26, 2016 at 04:51:35PM -0500, Yannick Warnier wrote: >> On an Ubuntu 15.10, following the docs at >> https://trac.xapian.org/wiki/FAQ/PHP%20Bindings%20Package >> >> When >> >> running debuild -e PHP_VERSIONS=5 -us -uc >> >> I get (sorry for the French): >> >> >> "
2004 May 11
0
Re: [Xapian-commits] Changes in xapian/xapian-bindings/ xapian/xapian-bindings/guile/ xapian/xapian-bindings/php4/ xapian/xapian-bindings/python/ xapian/xapian-bindings/tcl8/
On Tue, May 11, 2004 at 06:11:36PM +0100, Richard Boulton wrote: > "xapian-config --cxxflags" assumes that it doesn't need to emit > -I/usr/include in this situation (presumably on the basis that > any sane C compiler will already have that on its path). Worse, passing -I/usr/include causes problems with some versions of GCC on some platforms as GCC generates
2007 Oct 19
1
Re: [Xapian-commits] 9476: trunk/xapian-core/ trunk/xapian-core/include/xapian/ trunk/xapian-core/queryparser/ trunk/xapian-core/tests/
olly wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: olly > Revision: 9476 > Date: 2007-10-19 03:47:11 +0100 (Fri, 19 Oct 2007) > > Log message (14 lines): > include/xapian/queryparser.h,queryparser/queryparser.cc, > queryparser/queryparser.lemony,queryparser/queryparser_internal.h, > tests/queryparsertest.cc: Since calling
2019 Oct 22
5
It was twenty years ago today...
Xapian has turned 20! Strictly speaking it was 20 years ago last month but I managed to miss the true anniversary - the oldest commit in the Xapian repo is: commit 8ced76ea128c8fb2792477e09b41fa989f2e572f Author: Richard Boulton <richard at tartarus.org> Date: Fri Sep 10 09:50:40 1999 +0000 Martins initial code, which didn't work for him but did for me. Back then Richard,
2004 May 11
0
Re: [Xapian-commits] Changes in xapian/xapian-bindings/
On Tue, May 11, 2004 at 08:11:23PM +0100, Richard Boulton wrote: > Also, change tests for non-zeroness of interpreter paths to tests > for existence and executability of interpreter paths: this is > relevant if configure is passed an interpreter path by the user > which doesn't exist (as my debian packaging makefile just did). A problem is that "test -x"
2016 Jan 01
2
Xapian 1.3.4 development snapshot released
I'm happy to be able to announce that Xapian 1.3.4 is now available. Please note that 1.3.x releases are development releases - they are made to encourage earlier and wider use and testing of new and changed code. Our record with 1.1.x was very good - all the bugs I am aware of were either in new features, or were also present in the corresponding 1.0.x release. But if you main concern is
2007 Mar 08
1
Tarball size (was Re: [Xapian-commits] 7916: trunk/xapian-core/ trunk/xapian-core/docs/)
On Wed, Mar 07, 2007 at 11:22:36PM +0000, olly wrote: > docs/Makefile.am: Stop shipping docs/apidoc/latex/* in the > xapian-core tarballs since it's just useless bloat. Removing it > more than halves the size of the tarball (55% reduction!) Hmm, this is very odd. I tried unpacking the last xapian-core snapshot tarball, deleting the junk files, and rebuilding the tarball, and I got
2007 Jan 12
1
Re: [Xapian-commits] 7603: trunk/xapian-core/ trunk/xapian-core/backends/flint/ trunk/xapian-core/backends/quartz/
On Tue, Jan 02, 2007 at 03:55:59PM +0000, richard wrote: > * backends/quartz/btree.cc,backends/flint/flint_io.h: Patches from > Charlie Hull to allow 2GB+ index files work when compiled using > Visual C++. I suspect that xapian-compact.cc (and quartzcompact.cc if you can be bothered) will also need fixing since they use off_t. You need to make sure that the stat() function called
2007 Oct 07
1
Re: [Xapian-commits] 9389: trunk/xapian-core/ trunk/xapian-core/net/
On Mon, Oct 01, 2007 at 01:13:07PM +0100, richard wrote: > Log message (3 lines): > net/remoteconnection.cc: After calling read(), check for received > == 0 after checking for errors, so that if an EINTR occurs in > read, we don't report EOF instead of retrying. > [...] > http://xapian.org/C?9389?trunk/xapian-core/net/remoteconnection.cc I don't think this change is
2006 Dec 13
1
Re: [Xapian-commits] 7575: trunk/xapian-core/ trunk/xapian-core/include/xapian/
On Wed, Dec 13, 2006 at 06:09:49PM +0000, richard wrote: > Improve documentation comment for Document::get_value(). Further to this improvement, I wonder if the "must be >= 0" should be dropped. Xapian::valueno is an unsigned type, so you effectively can't pass a negative value in (if you do it'll be converted to a large positive value and would work if used
2007 Apr 17
1
Xapian commits list
The xapian commits list seems to be broken at the moment: several commits I did over the weekend and yesterday haven't shown up in it: the last message I saw was on Friday 13th April at 17:41. I'm not an administrator for that list - Olly/James, can you investigate? -- Richard
2006 Oct 04
1
Re: [Xapian-commits] 7283: trunk/xapian-core/ trunk/xapian-core/net/
On Wed, Oct 04, 2006 at 01:27:20PM +0100, richard wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: richard > Revision: 7283 > Date: 2006-10-04 13:27:17 +0100 (Wed, 04 Oct 2006) > > Log message (2 lines): > Use "unsigned char" instead of "char" when serialising lengths, to avoid > problems on platforms where char is