This benchmark application is designed to benchmark interactivity in Unix,
originally written by Con Kolivas et al. for Linux.
It is designed to measure the effect of changes in operating system kernel
design or system configuration changes such as CPU, I/O scheduler and file
system changes and options. With careful benchmarking, different hardware
can be compared.
===> The following configuration options are available for interbench-0.31_2:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Flush a short queue of minor non-functional changes sitting it my tree:
- Escape literal dot properly in sed(1) code (for REINPLACE_CMD)
- Spell "C-string" correctly in COMMENT and add a missing newline
- Use NULL for pointer in C code (original snippet was for C++ and Bjarne
prefers to avoid macros, per his C++ Style and Technique FAQ)
Reclaim maintainership of ports that I still use regularly, but decided to
relinquish at some point to allow contributions coming more easily (not to
impose hard lock). These days, there is no reason to yield maintainership
with the more lax rules and general consensus that casual changes do not
necessarily require explicit approval from maintainer prior to commit.
On the other hand, unmaintained ports can give (arguably false) impression
of being unwanted and one step above deprecation, yet these ports are not.
Inspired by: marino
- Unbreak parallel builds by separating cleaning and building
- Sort the knobs a bit while I am here
- Remove the check for old, unsupported versions of FreeBSD
- Relinquish control of the port, it's pretty safe to fly solo
Reported by: pointyhat-west
