Due to a change in the default system ld.library.path, these ports
fail to build due to not being able to find libjvm.so. Verified by
Redports, only openJDK6 can build these ports currently.
Approved by: gnome (kwm)
I tried to fix this port for modern C++ compilers, I really did. I
had come up with a couple of dozen patches and some REIMPLACE_CMD fixes
too. It almost compiled. I seemed to have lost that all those patches
since then though. tijl@ had a similar experience a few months ago.
This port was released by the maintainer 10 years ago. Among the reasons
stated was that maintainance was impossible to do correctly without access
to netflow-speaking routers. Also, no new release of the source code was
ever made, it's still in beta.
Therefore I recommend that this port requires a true maintainer, one that
has access to netflow routers. Given that the source was never updated, I
am not sure its even still useful 10 years later. So I recommend this
port be pruned on 15 August 2014 if no suitable maintainer shows up.
The port is also unstaged.
Related PR: ports/177211
Approved by: portmgr (implicit)
to sanity check port and adjust Makefile / pkg-plist accordingly.
Changes since 20140112:
* allow scamper to be built in debug mode on FreeBSD after version 10.
* in scamper-ping, support a probe frequency smaller than once every
second. minimum is now once a millisecond.
* handle fragmented responses in linux and sunos correctly.
this is important for IPv6 IP-ID based alias resolution techniques
(e.g. speedtrap, ally, radargun) on those platforms.
* numerous bugfixes and improvements to sc_ally pair-wise alias
resolution utility, the most important being that it will reliably
complete now.
* FreeBSD 10 onwards no longer byte swaps some fields in the quotation of
a received ICMP error message. chase this in scamper.
* Minor modifications to make scamper compile on Windows 7 using
Visual Studio Express 2013 for Windows Desktop.
* print ping flags in sc_wartsdump and scamper's json output.
PR: 190440
Submitted by: maintainer
o) www/rubygem-passenger;
o) third-party modules for www/nginx and www/nginx-devel.
<ChangeLog>
Release 4.0.44
--------------
* The issue tracker has now been moved from Google Code to Github.
Before version 4.0.44 (May 29 2014, commit 3dd0964c9f4), all
issue numbers referred to Google Code. From now on, all issue
numbers will refer to Github Issues.
* Fixed compilation problems on OS X Lion and OS X Mountain Lion.
* On Ruby, fixed `nil` being frozen on accident in some cases.
See issue #1192.
Release 4.0.43
--------------
* Introduced a new command `passenger-config list-instances`, which prints all
running Phusion Passenger instances.
* Introduced a new command `passenger-config system-metrics, which displays
metrics about the system such as the total CPU and memory usage.
* Fixed some compilation problems caused by the compiler capability autodetector.
* System metrics such as total CPU usage and memory usage, are now sent to
[Union Station](https://www.unionstationapp.com) in preparation for future
features.
Release 4.0.42
--------------
* [Nginx] Upgraded the preferred Nginx version to 1.6.0.
* [Nginx] Fixed compatibility with Nginx 1.7.0.
* [Standalone] The MIME type for .woff files has been changed to application/font-woff.
Fixes issue #1071.
* There are now APT packages for Ubuntu 14.04. At the same time, packages for
Ubuntu 13.10 have been abandoned.
* Introduced a new command, `passenger-config build-native-support`, for ensuring
that the native_support library for the current Ruby interpreter is built. This
is useful in system provisioning scripts.
* For security reasons, friendly error pages (those black/purple pages that shows
the error message, backtrace and environment variable dump when an application
fails to start) are now disabled by default when the application environment is
set to 'staging' or 'production'. Fixes issue #1063.
* Fixed some compilation warnings on Ubuntu 14.04.
* Fixed some compatibility problems with Rake 10.2.0 and later.
See [Rake issue 274](https://github.com/jimweirich/rake/issues/274).
* Improved error handling in [Union Station](https://www.unionstationapp.com) support.
* Data is now sent to Union Station on a more frequent basis, in order to make new
data show up more quickly.
* Information about the code revision is now sent to Union Station, which will be
used in the upcoming deployment tracking feature in Union Station 2.
</ChangeLog>
Fix lua/luajit-specific extra patches.
Stagefy.
<ChangeLog>
--[ Redis 3.0.0 Beta 5 (version 2.9.54) ] Release date: 26 may 2014
This is the 5th beta of Redis 3.0.0. It does not include any real
worthwhile change (just three days passed since the previous beta), but
fixes two stupid bugs preventing cluster tests to pass.
--[ Redis 3.0.0 Beta 4 (version 2.9.53) ] Release date: 23 may 2014
This is the fourth beta of Redis 3.0.0.
>> General changes
* [NEW] Scripting engine performances improvements.
* [NEW] Log format slightly changed to report current node role.
* [FIX] Correct the HyperLogLog stale cache flag to prevent unnecessary
computation.
>> Cluster changes
* [NEW] redis-trib: ability to import data from standalone Redis instances.
* [NEW] redis-trib: "fix" subcommand much better at fixing errors.
* [NEW] CLUSTER FAILOVER FORCE implemented.
* [NEW] CLUSTER RESET implemented, it is now possible to completely reset
nodes and create a new cluster without restarting anything.
* [NEW] Slave validity factor (max estimated data age to still failover)
is now under the control of the user, and can be configured via
redis.conf or CONFIG SET. Option name cluster-slave-validity-factor.
* [NEW] Cluster test: failure detection and failover initial tests.
* [NEW] CLUSTER MEET: better error messages when address is invalid.
* [NEW] Bulk-accept new Cluster nodes in the Cluster bus instead of
performing just a single accept() per event fired.
* [FIX] Bypass data_age check for manual failovers.
* [FIX] Fixed data_age computation / check integer overflow.
* [FIX] Various fixes to Tcl client.tcl Redis Cluster client used in tests.
* [FIX] Better handling of stolen slots.
* [FIX] Don't accept cluster bus connections during startup.
>> Sentinel changes
* [NEW] Generate +config-update-from event when a new config is received.
* [NEW] Log when a failover will be re-attempted again.
* [FIX] Sentinel: Add "dir /tmp" directive in example sentinel.conf.
--[ Redis 3.0.0 Beta 3 (version 2.9.52) ] Release date: 5 may 2014
This is the third beta of Redis 3.0.0.
>> General changes
* [NEW] New data structure: the HyperLogLog (see 2.8 release notes).
* [NEW] Lexicograhical range queries in sorted sets (see 2.8 release notes).
* [NEW] LRU algorithm precision greatly improved.
* [FIX] Redis is now much more responsive to reply with LOADING / BUSY errors.
>> Cluster changes
* [NEW] Cluster testing framework and initial tests.
* [NEW] Cluster epochs collision resolution (make Redis Cluster more resilient
to admin and programming errors).
* [NEW] Persist / fsync some global state to ensure correct crash-recovery
semantics.
* [NEW] New command introduced: CLUSTER SET-CONFIG-EPOCH, still not used
by redis-trib. Will be used to speedup the assignment of unique
epochs to different nodes at cluster creation time. For now this is
handled as a side effect of the cluster epochs collision resolution.
* [FIX] Different fixes to redis-trib cluster creation.
* [FIX] Fix an error in the CLUSTER NODES output for nodes slots.
>> Sentinel changes
* [NEW] Sentinels are now able to send update messages in a peer-to-peer
fashion even if no Redis instances are available. Now the Sentinel
liveness property that the most updated configuration in a given
partition is propagated to all the Sentinels is extended to partitions
without reachable instances.
* [NEW] Sentinel safety properties are now ensured in a crash-recovery system
model since some state is persisted on disk before replying to other
nodes, and reloaded at startup.
* [NEW] Sentinel now uses CLIENT SETNAME so that it is easy to identify
Sentinels using CLIENT LIST among other clients.
* [NEW] Sentinel failure detection and reconnection code improved.
</ChangeLog>
