freebsd-ports-gnome - FreeBSD GNOME current development ports (https://github.com/freebsd/freebsd-ports-gnome)

	Commit message (Collapse)	Author	Age	Files	Lines
*	Python cleanup:	Rene Ladan	2014-01-14	1	-1/+1
\| \| \| \| \| \| \|	- USE_PYTHON* = 2.X -> USE_PYTHON* = 2 - USE_PYTHON* = 2.X+ -> USE_PYTHON* = yes Reviewed by: python (mva, rm) Approved by: portmgr-lurkers (mat)
*	Remove LATEST_LINK from my ports and fix CONFLICTS for lang/pypy.	David Naylor	2013-12-11	1	-2/+0
\|
*	Add stage support to lang/pypy, lang/pypy-devel and lang/pypy3-devel.	David Naylor	2013-11-07	1	-17/+8
\| \| \| \| \| \|	Also, require a modern compiler that can handle c11. Although this is not strictly required (just about any C compiler would do) the base GCC compiler has a memory bug and thus cannot reasonably compile the ports.
*	Add NO_STAGE all over the place in preparation for the staging support (cat: ↵	Baptiste Daroussin	2013-09-21	1	-0/+1
\| \| \| \|	lang)
*	Fix the pypy ports.	David Naylor	2013-08-13	1	-1/+2
\| \| \| \| \| \| \| \| \| \| \| \|	Be more aggresive in cleaning up temporary directories that pypy leaves behind in the copied directories (files and directories in __pycache__). Only .so and .pyc should be left behind in those __pycache__ directories and no subdirectories. Also remove the manual requirement for building lang/pypy. Redports successfully built lang/pypy3-devel (with leftovers) in 19 hours. Reported by: Redports
*	Backport and fix-up lang/pypy* ports.	David Naylor	2013-08-12	2	-3/+30
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	pypy: - fix sysconfig.py's include path - bump PORTREVISION due to above fix pypy-devel: - remove duplicate '-e' when creating pkg-plist - ancillary port functionality (thus no PORTREVISION bump) pypy3-devel: - add missing patch - fix pkg-plist - build fails without above patch (thus no PORTREVISION bump)
*	Introducing lang/pypy3-devel version 2.1.b1.	David Naylor	2013-08-12	14	-0/+3635
	Highlights - The first release of PyPy3: support for Python 3, targetting CPython 3.2.3! - There are some known issues including performance regressions (issues #1540 & #1541) slated to be resolved before the final release.