non port: x11-toolkits/py-wxPython30/Makefile |
Number of commits found: 22 |
Sunday, 17 May 2020
|
05:55 lbartoletti
x11-toolkits/wxgtk30: Update to 3.0.5.1
Changelog:
-
https://raw.githubusercontent.com/wxWidgets/wxWidgets/v3.0.5/docs/changes.txt
PR: 246218
Approved by: tcberner (mentor)
Exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D24808
|
Sunday, 1 Mar 2020
|
10:20 antoine
Deprecate py-wxPython28 and py-wxPython30 ports
With hat: portmgr
|
Friday, 26 Jul 2019
|
20:46 gerald
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
|
Monday, 27 May 2019
|
11:40 ak
- Remove no-op (since r397077) WANT_UNICODE variable from the ports tree
Approved by: portmgr blanket
|
Monday, 25 Feb 2019
|
12:47 bapt
wxGTK3.0: switch to gtk3 and webkit2
Discussed with: portmgr
|
Wednesday, 12 Dec 2018
|
01:35 gerald
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
|
Sunday, 29 Jul 2018
|
22:18 gerald
Bump PORTREVISION for ports depending on the canonical version of GCC
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
|
Wednesday, 20 Jun 2018
|
17:05 mat
Use PY_FLAVOR for dependencies.
FLAVOR is the current port's flavor, it should not be used outside of
this scope.
Sponsored by: Absolight
|
Thursday, 30 Nov 2017
|
15:50 mat
Convert Python ports to FLAVORS.
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the
current python flavor. It can be used in dependency lines when the
port itself is not python flavored. For example, deskutils/calibre.
By default, all the flavors are generated. To only generate flavors
for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define
BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf.
In all the ports with Python dependencies, the *_DEPENDS entries MUST
end with the flavor so that the framework knows which to build/use.
This is done by appending '@${PY_FLAVOR}' after the origin (or
@${FLAVOR} if in a Python module with Python flavors, as the content
will be the same). For example:
RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR}
PR: 223071
Reviewed by: portmgr, python
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D12464
|
Sunday, 10 Sep 2017
|
20:55 gerald
Bump PORTREVISION for ports depending on the canonical version of GCC
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
|
Wednesday, 19 Apr 2017
|
07:18 miwi
- Fix shebang
|
Saturday, 1 Apr 2017
|
15:23 gerald
Bump PORTREVISIONs for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using using Mk/bsd.octave.mk which in turn has USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
c++11-lang, c++0x, c11, or gcc-c++11-lib.
PR: 216707
|
Friday, 23 Sep 2016
|
09:01 rm
x11-toolkits/py-wxPython30: install header files
These headers are required to build some ports.
PR: 211310
Reported by: yuan.mei@gmail.com
With hat: python
|
Friday, 1 Apr 2016
|
14:33 mat
Remove ${PORTSDIR}/ from dependencies, categories v, w, x, y, and z.
With hat: portmgr
Sponsored by: Absolight
|
Friday, 1 Jan 2016
|
06:35 sunpoet
- Use DISTVERSIONPREFIX instead of DISTNAME
- Use WRKSRC_SUBDIR instead of WRKSRC
|
Tuesday, 14 Apr 2015
|
06:43 marino
x11-toolkits/py-wxPython30: Fix c++ code, drop gcc requirement
While here, upgrade from version 3.0.0 to 3.0.2
wxPython30 was obligated to build under c++11 standards, but the code
was not compliant. It now builds on system clang again.
PR: 199403
Submitted by: matthew (reztec.cz)
Approved by: blanket (fixes previous "fix")
|
Sunday, 12 Apr 2015
|
07:03 marino
x11-toolkits/py-wxPython30: Unbreak on F10
It turns out that wxPython30 won't build with clang at all. The c++ code
is illegal according to clang (e.g. illegal cast), so remove the
USES=compiler setting and replace with USE_GCC=yes. Tested on F8 and F10.
I apologize for adding the GCC dependence for F10+ users but I didn't see
any other simple fix.
Approved by: blanket
|
Saturday, 11 Apr 2015
|
20:30 marino
x11-toolkits/py-wxPython30: Unbreak on F8 and F9
This port must be built under c++11 standard like the rest of the
wx-dependent ports. I couldn't find a way to pass the flag so I had
to patch the python script directly. Also, the USES=compiler setting
was missing, which is required to actually pull in a c++11 capable
compiler on the older FreeBSD releases.
This port was blocking ~29 other ports from building on releases that
it wouldn't build on.
Approved by: blanket
|
Sunday, 19 Oct 2014
|
18:16 mva
- Convert ports from korean/, shells/, x11/, x11-clocks/, x11-fm/,
x11-fonts/, x11-toolkits and x11-wm to new USES=python
Approved by: portmgr (implicit)
|
Wednesday, 10 Sep 2014
|
20:50 gerald
Update the default version of GCC in the Ports Collection from GCC 4.7.4
to GCC 4.8.3.
Part II, Bump PORTREVISIONs.
PR: 192025
Tested by: antoine (-exp runs)
Approved by: portmgr (implicit)
|
Saturday, 5 Jul 2014
|
21:54 wg
x11-toolkits/py-wxPython-common: fix python compile to use non-stage path
|
18:22 wg
Introduce x11-toolkits/py-wxPython30
x11-toolkits/py-wxPython28 was been modified to do not install wxversion python
files which conflict with wxPython30. Instead a new port has been created
(x11-toolkits/py-wxPython-common) which only installs wxversion and wx.pth
responsible for selecting the wxPython version.
Stage support has been added to all related ports.
Maintainership has been reset to python@.
The final goal is to make all ports use wxPython30 so we can remove wxPython28.
|
Number of commits found: 22 |