Bugzilla Bug 88638

"The Google SparseHash project contains several hash-map implementations in use
at Google, with different performance characteristics, including an
implementation that optimizes for space and one that optimizes for speed."

Need a hash-map for my project, figured I'd add this to Portage.

Created an attachment (id=55914) [edit]
sparsehash-0.1.ebuild

Created an attachment (id=61332) [edit]
sparsehash-0.2.ebuild

In case anyone's worried about adding more to their workload, this is a very
trivial package. All it contains is a few include files and some docs to go
with them.

Version 0.2 is now out. The ebuild only needed to be renamed but here it is
anyway.

Please fix the following and reopen:

* Header is incorrect.
* ${D} should be quoted.
* IUSE needed.

Created an attachment (id=66269) [edit]
sparsehash-0.2.ebuild

Okay.

Oops, looked like I missed one other thing:

* We don't usually use emake for install targets because it can have problems
parallelising.

I think that's the last. Please reopen with a fixed ebuild and I'll tag this as
reviewed.

Created an attachment (id=66307) [edit]
sparsehash-0.2.ebuild

Happy now?

Waah! How did I miss this one?

* http://dev.gentoo.org/~ciaranm/docs/mw-faq/redundant.txt (src_compile)

Please reopen with an attached ebuild. Sorry, I should've noticed this one
straight off.

Created an attachment (id=68380) [edit]
sparsehash-0.2.ebuild

Created an attachment (id=82583) [edit]
sparsehash-0.3.ebuild

Version bump.

Created an attachment (id=91432) [edit]
ebuild

It's exactly the same as mine...?

Created an attachment (id=91435) [edit]
ebuild

(From update of attachment 91432 [edit])
sorry for the double attachment, bugzilla seems to be _really_ slow

(In reply to comment #13)
> It's exactly the same as mine...?
> 

yes, it's just a version bump to 0.4

reassigning for closing.

Version 1.0 is now in CVS.