[Xapian-tickets] [Xapian] #361: Some --disable-backend-XXX option combinations fail
Xapian
nobody at xapian.org
Sun Jun 6 14:37:16 BST 2010
#361: Some --disable-backend-XXX option combinations fail
--------------------------+-------------------------------------------------
Reporter: olly | Owner: olly
Type: defect | Status: assigned
Priority: normal | Milestone: 1.2.1
Component: Build system | Version: 1.1.0
Severity: normal | Keywords:
Blockedby: | Platform: All
Blocking: |
--------------------------+-------------------------------------------------
Comment(by olly):
Well, some of them now work.
The rest seems to be a nightmare - replication uses lots of remote backend
stuff, as do serialise methods. I started to add #ifdef-s, but it seems
too complex to be worthwhile, and is too easy to regress unless we're
prepared to check all 32 build combinations regularly. We can probably
trim that down some, but it's likely to be
at least 10 to cover combinations likely to be problematic.
So I'm tending to think we should seriously consider removing these
options. They're useless for binary packaging (since somebody will want
any given backend), so the only real use I can see is for people building
a custom "small" Xapian for use of restricted hardware (e.g. embedded
systems). If we want to assist that, the best way is probably an option
which gives you just one disk based backend, and perhaps a second which
disables the remote backend and replication. But perhaps we should worry
about this if/when we actually have someone wanting it. It seems nobody
is regularly using the current options to disable backends as I've
generally found them broken when I've tried them.
--
Ticket URL: <http://trac.xapian.org/ticket/361#comment:4>
Xapian <http://xapian.org/>
Xapian
More information about the Xapian-tickets
mailing list