Olly Betts | 1 Sep 12:47
Favicon
Gravatar

Re: xapian-core-1.1.2 build error

On Tue, Sep 01, 2009 at 04:09:18PM +0800, Liu Haifeng wrote:
> when building 1.1.2, I just get the following error:
> 
> ./common/safeuuid.h: In function `void uuid_unparse_lower(const unsigned
> char*, char*)':
> ./common/safeuuid.h:37: error: invalid type argument of `unary *'
> 
> 
> Is it a bug? Seems you wanna write  *(out + i) |= 0x20; 

This is a bug in the fix for #368:

http://trac.xapian.org/ticket/368

Fixed in r13438 (I used out[i] but your version is equivalent).

Thanks for your report.

Cheers,
    Olly
Olly Betts | 3 Sep 02:43
Favicon
Gravatar

Re: [Xapian-commits] 13440: trunk/xapian-core/ trunk/xapian-core/matcher/ trunk/xapian-core/tests/

On Thu, Sep 03, 2009 at 01:32:48AM +0100, richard wrote:
> matcher/andmaybepostlist.cc: For AndMaybe, if the RHS has a
> maximum possible weight of 0, we now decay to just the LHS.
> tests/Makefile.am,tests/api_queryopt.cc: Test coverage that this
> optimisation doesn't break anything.

I can see two problems with this optimisation:	

Firstly, it means that count_matching_subqs() will return one less
when the RHS would have matched, giving lower than expected percentage
weights in some cases.

Secondly, if under OP_SYNONYM, the wdf of the RHS will get ignored.

Cheers,
    Olly
Ben Walton | 10 Sep 19:34
Picon
Picon

[PATCH] support ruby in the xapian-bindings rpm spec


Hi All,

I've needed to build ruby bindings for xapian recently and discovered
that the default .spec file doesn't support ruby by default.  The
attached patch adds this support to the spec file in a manner
consistent (I think) with the other bindings.

I hope you find this useful.

Thanks
-Ben
--

-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
_______________________________________________
Xapian-devel mailing list
Xapian-devel <at> lists.xapian.org
http://lists.xapian.org/mailman/listinfo/xapian-devel
Olly Betts | 11 Sep 02:56
Favicon
Gravatar

Re: [PATCH] support ruby in the xapian-bindings rpm spec

On Thu, Sep 10, 2009 at 01:34:23PM -0400, Ben Walton wrote:
> I've needed to build ruby bindings for xapian recently and discovered
> that the default .spec file doesn't support ruby by default.  The
> attached patch adds this support to the spec file in a manner
> consistent (I think) with the other bindings.

Thanks, applied to trunk as r13483 and branches/1.0 as r13485.

BTW, the .spec is generated - it's actually .spec.in that needs
patching.

Cheers,
    Olly
Ben Walton | 11 Sep 05:18
Picon
Picon

Re: [PATCH] support ruby in the xapian-bindings rpm spec

Excerpts from Olly Betts's message of Thu Sep 10 20:56:48 -0400 2009:
> BTW, the .spec is generated - it's actually .spec.in that needs
> patching.

Doh!  Thanks for pointing that out.  I just grabbed the .spec from the
tarball and modified it to build.

Thanks
-Ben
--

-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
_______________________________________________
Xapian-devel mailing list
Xapian-devel <at> lists.xapian.org
http://lists.xapian.org/mailman/listinfo/xapian-devel
Ben Walton | 11 Sep 15:17
Picon
Picon

rhel5 rpms


Hi All,

If there is interest, I'd be happy to make my rhel5 rpms available for
others.  I currently have x86, but I could whip up x86_64 too if it
would help.

Thanks
-Ben
--

-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
_______________________________________________
Xapian-devel mailing list
Xapian-devel <at> lists.xapian.org
http://lists.xapian.org/mailman/listinfo/xapian-devel
Steve Huff | 17 Sep 15:09
Gravatar

Re: Fink package for xapian-bindings (Python)


On May 11, 2009, at 11:21 PM, Steve Huff wrote:

> on this page (http://xapian.org/download) you have links to the Fink  
> packages for xapian-core and omega; you may be interested to know  
> that i've packaged the Xapian Python bindings.  i'm working on  
> similar packages for the Ruby and PHP bindings, and i'd be happy to  
> inform you once they've been pushed out to the mirrors.

thank you for updating the download page to mention the Python  
bindings and omega; i have also packaged the Ruby bindings.  Fink's  
core Xapian packages are currently at 1.0.16; my bindings are still at  
1.0.12, but i have already submitted the updates to 1.0.16 and am  
waiting for the Fink team to process the submission.

-steve

--
If this were played upon a stage now, I could condemn it as an  
improbable fiction. - Fabian, Twelfth Night, III,v
http://five.sentenc.es

_______________________________________________
Xapian-devel mailing list
Xapian-devel <at> lists.xapian.org
http://lists.xapian.org/mailman/listinfo/xapian-devel
Steve Huff | 17 Sep 15:16
Gravatar

Xapian packages in rpmforge?

hello folks!

i've recently joined the rpmforge maintainers; given that Tim Brody  
has already written specfiles for RHEL4 and RHEL5, would you be  
interested in my adding the xapian packages to rpmforge?  this would  
eliminate (or at least reduce) the need for you to maintain a separate  
repository and would mean that many users (those who have already  
configured their systems to pull packages from rpmforge) would have a  
turnkey installation of Xapian.

i found the SRPMs in http://xapian.org/RPM/centos5/SRPMS/, so i don't  
think i'll need any further technical assistance in porting the  
packages, but i wanted to check in with you first.  thoughts?

-steve

--
If this were played upon a stage now, I could condemn it as an  
improbable fiction. - Fabian, Twelfth Night, III,v
http://five.sentenc.es

_______________________________________________
Xapian-devel mailing list
Xapian-devel <at> lists.xapian.org
http://lists.xapian.org/mailman/listinfo/xapian-devel
Olly Betts | 17 Sep 16:22
Favicon
Gravatar

Re: Fink package for xapian-bindings (Python)

On Thu, Sep 17, 2009 at 09:09:55AM -0400, Steve Huff wrote:
> thank you for updating the download page to mention the Python bindings 
> and omega; i have also packaged the Ruby bindings.  Fink's core Xapian 
> packages are currently at 1.0.16; my bindings are still at 1.0.12, but i 
> have already submitted the updates to 1.0.16 and am waiting for the Fink 
> team to process the submission.

Cool.  I've updated the download page locally, which should prompt me to
notice and check if the Ruby packages have gone live next time I make a
release or update it for some other reason.

Cheers,
    Olly
Olly Betts | 18 Sep 07:47
Favicon
Gravatar

Re: Xapian packages in rpmforge?

On Thu, Sep 17, 2009 at 09:16:28AM -0400, Steve Huff wrote:
> i've recently joined the rpmforge maintainers; given that Tim Brody has 
> already written specfiles for RHEL4 and RHEL5, would you be interested in 
> my adding the xapian packages to rpmforge?  this would eliminate (or at 
> least reduce) the need for you to maintain a separate repository and 
> would mean that many users (those who have already configured their 
> systems to pull packages from rpmforge) would have a turnkey installation 
> of Xapian.

I don't know anything about rpmforge (and their website doesn't seem to
offer a useful high-level view of what they are, while wikipedia
redirects rpmforge to the middle of the fedora article, which doesn't
mention rpmforge at all).  I also don't use RPMs myself.

So I don't feel I can usefully have an opinion.  I'd talk to Tim and
Fabrice Colin and see what they think.

> i found the SRPMs in http://xapian.org/RPM/centos5/SRPMS/, so i don't  
> think i'll need any further technical assistance in porting the  
> packages, but i wanted to check in with you first.  thoughts?

There are spec files in the source tarballs, which I think are what the
RPMs in xapian.org/RPM use.  If they need changes, please do send in
patches (in each case .spec is actually generated from .spec.in, just
so that the package name and version update automatically - patches
against either are OK).

Cheers,
    Olly
(Continue reading)


Gmane