Bugzilla Bug 78727

dspam doesn't work with sqlite-3 and portage has a "bug" that won't let you do
something like this:
DEPEND= ">=dev-db/sqlite-2.7.7 
 < dev-db/sqlite-3"

So if you don't have any sqlite installed and you use a KEYWORD supported by
the sqlite-3 ebuilds, portage will emerge sqlite-3 instead of 2.

If you are interested Dan Armak (kde herd) made a workaround to do this, it's
in the kde-functions.eclass and I think it can be easily used by other ebuilds.

I wasn't totally clear. Reading from the dspam-3.4_beta readme, it support also
sqlite-3, but the ebuilds doesn't enable it and uses only sqlite-2 configure
options.

What I said before doesn't change, you always need a workaround to use ranged
dependencirs.

But I'll also suggest to add a new use "sqlite3" to enable its support.
I'm alreading doing the same with dev-db/hk_classes latest ebuilds: the
"sqlite" use flag enables the sqlite-2 support, while the "sqlite3" enables
sqlite-3 support. 

Easily? Hardly...

That workaround is the deprange() function from kde-functions.eclass. It
receives as parameters a minimal and maxiumm version and a package name and
generates an || dep that includes all possible versions in between.

That's 1) ugly, 2) last-resort (for me anyway) until portage gets real deprange
support and 3) tied to the KDE versioning scheme: currently it only supports
x.y.z version numbers, with only z (and suffixes like _beta, and ebuild
revs) changing between the items in the ||-list.

But if there's interest, I could expand its interface to allow for any
boundaries/version formats by using =foo-ver* atoms. However I'm uneasy at the
thought of widespread deprange() usage outside the kde ebuilds. The portage
people might really get mad at me this time :-)

Ooops,
  The beta does have support for sqlite-3 but previous dspam packages did not.  Since this is a new support thing, I'll probably need to test it some more.  But if you do want to use dspam with sqlite-3, can someone just edit the ebuild and test it?

  I'll appreciate any other person's testing this dependency for me. :)

Regards
Lim Swee Tat

Someone did test sqlite3 support, and I'm rolling it in.