Release update for further testing by community.
Change Log:
- Reduced internal copying of bytearray operations
- Tweak the internal structure of StringBuilder to speed up large string
handling, which becomes advantageous on large programs at the cost of
slightly slower small benchmark type programs.
- Move to a mixed polling and mutex GIL model that make mutlithreaded jitted
code run much faster
- Remove ctypes pythonapi and ctypes.PyDLL, which never worked on PyPy
- Fix performance regression on ufunc(<scalar>, <scalar>) in numpy
- Classes in the ast module are now distinct from structures used by the
compiler, which simplifies and speeds up translation of our source code to
the PyPy binary interpreter
- Upgrade stdlib from 2.7.5 to 2.7.8
Portlint's history goes back to itojun. I've researched his open source
projects and he either used two licenses:
BSD3CLAUSE: magicpoint, sch
His own license: portlint, snooper, various camera tools, etc
Debian asked him years ago about his license to see if it complies with
thier DFSG:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=88416
Example of his license:
Copyright(c) 1997 by Jun-ichiro Hagino <itojun@itojun.org>.
All rights reserved.
Freely redistributable. Absolutely no warranty.
OR
Absolutely no warranty. Pray before try. Freely redistributable.
Hope I'm not crossing any boundaries here, but in my effort to clean up
"BSD" licenses in the ports tree this one certainly is not and sadly we
can't just ask him.
Some users of Nvidia cards reports very high cpu usage by ecore_x_vsync,
in this case devel/efl should be rebuild with NVIDIA option enabled.
Submitted by: 6yearold <at> gmail <dot> com (via email)
This port was added on 5 October 2014. The intention for its existence
was to provide a way to use plv8js with pgsql 9.3 instead of the default
pgsql 9.2. It was implemented in such a way that if PGSQL_DEFAULT is
set to 9.3, the index breaks with a duplicate origin with datbases/
postgresql-plv8js. It's possible to adjust the plv8js ports by converting
the version into an option and using typical master/slave techniques, but
I can't come up with a good reason to do this at all.
I don't think this port ever should have been created. Anyone that would
need this port would have needed to set PGSQL_DEFAULT anyway (which
already works). In the worst case, WANT_PGSQL could be based through a
command line. Perhaps the motivation was to have a binary package to
avoid building it, but this reason disappears soon when the default
version of pgsql is bumped to 9.3. Based on all those reasons, I think
it is better to remove the port outright (pointing to master port) rather
than adjust it to avoid a broken index.
PR: 195281
As the result of a recent exp-run for postgresql 9.3, several ports
failed to build as a result. Most could likely be fixed by updating the
port to a later available version. Until that happens, set the maximum
version of pgsql to 9.2 for these ports.
* pg_rman (1.23) : version 1.27 is available
* pg_statsinfo (2.4.1) : version 2.5.0 available, works on pgsql 9.3
* pgpool-II (3.1.6) : version 3.4 available, works on pgsql 9.3
* pgpool-II30 (3.0.4)
PR: 195281
