An extremely memory-efficient hash_map implementation. 2 bits/entry overhead!
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.
WWW: http://code.google.com/p/google-sparsehash
===> The following configuration options are available for google-sparsehash-2.0.2_2:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
devel/google-sparsehash: Upgrade to 2.0.3 and rename to devel/sparsehash
* The project was moved from Google Code to GitHub (unbreak), hinted by [1]
* Upgrade from 2.0.2 to 2.0.3
* Remove now unneeded patches
* Remove the requirement for C++11 - the code does not need it
* Use PREFIX instead of LOCALBASE as a destination directory
PR: 213093 [1]
Submitted by: Erik Nordstrom <erik@nordstroem.no> [1]
GOOGLE_CODE has gone away.
- If a port has another upstream, remove GOOGLE_CODE
- If a port only has GOOGLE_CODE mark it BROKEN
Some ports have a local mirror configured but for security reasons, it
is not considered upstream.
Sponsored by: Absolight
MASTER_SITES cleanup.
- Replace ${MASTER_SITE_FOO} with FOO.
- Merge MASTER_SITE_SUBDIR into MASTER_SITES when possible. (This means 99.9%
of the time.)
- Remove occurrences of MASTER_SITE_LOCAL when no subdirectory was present and
no hint of what it should be was present.
- Fix some logic.
- And generally, make things more simple and easy to understand.
While there, add magic values to the FESTIVAL, GENTOO, GIMP, GNUPG, QT and
SAMBA macros.
Also, replace some EXTRACT_SUFX occurences with USES=tar:*.
Checked by: make fetch-urlall-list
With hat: portmgr
Sponsored by: Absolight
Remove indefinite articles and trailing periods from COMMENT, plus
minor COMMENT typos and surrounding whitespace fixes. Categories D-F.
CR: D196
Approved by: portmgr (bapt)
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
(Only the first 15 lines of the commit message are shown above )
Forced commit to note that the last commit message should read:
"Upgrade devel/google-sparsehash from 0.6 to 0.7"
Spotted by: "Vanilla I. Shu" <vanilla@fatpipi.cirx.org>
* Upgrade devel/google-sparsehash from 0.4 to 0.5
* Add copy of the distfile to the FreeBSD mirrors:
sometimes I receive a notice from fenner@ that the distfile is not fetchable,
but fetch has never failed when I tried to reproduce that. Add the mirrors
just to be on the safe side.
* Update from 0.3 to 0.4
* Remove @ prefix from the shell commands so users can see what's happening
* Rename target `tests' to `check' to conform with the software's own target
* Sync plist
Add google-sparsehash.
An extremely memory-efficient hash_map implementation. 2 bits/entry overhead!
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.
WWW: http://goog-sparsehash.sf.net
PR: ports/82696
Submitted by: Vasil Dimov <vd@datamax.bg>
