Unfortunately, this also affects some ports using QT3 as a GUI toolkit.
Changes to infrastructure files:
- bsd.kde.mk : obsolete, remove
- bsd.qt.mk : note that a CONFLICTS_BUILD line can probably go after a while
- CHANGES : document the removals from bsd.port.mk
- KNOBS : remove KDE and QT (KDE4 and QT4 should be used instead)
- MOVED : add the removed ports
PR: ports/180745
Submitted by: rene
Approved by: portmgr (bapt)
Exp-run by: bapt
- Remove options in ${OPTIONS_NAME}_(UN)SET from NEW_OPTIONS list.
- Remove an intermediate sort.
- Add support for ${OPTIONS_NAME}_(UN)SET_FORCE.
Approved by: bapt
Add a new macro to allow a port to limit itself the maximum numbers of jobs allowed [2]
Submitted by: danfe (based on) [1]
pgj (base on) [2]
Reviewed by: bdrewery, miwi
Multiple exp-run: bapt
- Update devel/gettext to 0.18.3
- Fix known-broken (from exp-runs) ports
- Clean up a lot of cruft in the devel/gettext port itself,
based on work from tijl@
PR: 178883
Submitted by: ade
Sponsored by: Wadsworth 6X
a CNAME to codeload and has been communicated to me from github staff
as being the same. Despite this, it is currently returning errors.
With hat: portmgr
While I'm here, also trim the headers on a couple of ports and remove
a reference to the Dragonlace mirror which is down indefinitely.
Approved by: bapt (mentor)
optiondir being defined in a subshell wasn't defined when the error message is printed.
PR: ports/176849
Submitted by: Oleg Ginzburg <olevole@olevole.ru>
libname.so:${PORTSDIR}/devel/name
libname.so.0.1.2:${PORTSDIR}/devel/name
This syntax is support to replace the old syntax and code which has multiple weakness:
It was replying on ldconfig -r which arbritrary limited our valid library to name of the following form:
libname.so[.X] where X can be a number
foo.3 could match both libfoo.3.do and libfoo.so.3
Reviewed by: bdrewery, danfe, miwi
Pkg-1.1.4 will define UID=0 when sourcing bsd.pkgng.mk directly.
This extra defined(UID) can eventually be removed, but is needed
for backwards compatibility for now.
Reported by: uqs
Reviewed by: bapt
With hat: portmgr
Proudly brought to you by the KDE on FreeBSD team. We're sorry to ship two
KDE updates in just a few days, but the work on 4.10.5 was very light
compared to 4.10.4 so it was ready much faster.
The release announcement can be found in [1].
[1] http://www.kde.org/announcements/announce-4.10.5.php
The biggest news for us on FreeBSD is that the Ruby bindings should work
with Ruby 1.9 now.
I will probably add a note to UPDATING later about this, but as avilla@
pointed out, the clang support we mentioned that was improved in 4.10.4
requires a rebuild of the ports that depend on kdelibs4. Most of them are
covered by this update, but those which are not part of the Software
Compilation need to be rebuilt manually to make sure the previous issues
(proper symbol visibility being the most annoying of them) are solved.
With commits from avilla@, makc@, rakuco@ and Schaich Alonso.
The upstream announcement can be found in [1].
[1] http://www.kde.org/announcements/announce-4.10.4.php
clang support should be more stable now, with clang being recognized by
kdelibs4 and being passed the correct flags to build other ports.
Additionally, all ports being committed have been verified to build with
-CURRENT's clang 3.3 on an amd64 tinderbox (special thanks go to swills@ for
providing it).
Work on the newly-released 4.10.5 will begin shortly.
system currently installed (i.e. PYEASYINSTALL_ARCHDEP) the entire version
string of the system is used in the destination directory, for example;
python_ldap-2.4.12-py2.7-freebsd-10.0-CURRENT-amd64.egg
This plays havoc when STABLE, RELEASE and RELENG are used, not forgetting
patchlevels as well. Now, only the major FreeBSD version number is included;
python_ldap-2.4.12-py2.7-freebsd-10-amd64.egg
Given that ABI should be stable at least over major releases, this now allows
packages to be created and installed correctly.
PR: ports/133081
Submitted by: Stef Walter <stef@memberwebs.com>
(this patch used as a starting point)
Reviewed by: No objections from python@
This uses accept 'env' as an argument for ports that do use their own or a different do-configure target.
Modify xmkmf so it accept IMAKECPPFLAGS as default flags for imake and pass it to the called imake.
Modify xorg-cf-files (the FreeBSD.cf configuration file) to allow CppCmd to be overwritten.
Pass CppCmd CcCmd and CplusplusCmd via command line to each call of imake via IMAKECPPFLAGS
Pass IMAKE_DEFINE with the above arguments to MAKE_ARGS so that imake spawned from Makefile generated by a previous
imake also inherit the defined CppCmd CcCmd and CplusplusCmd.
Make imake use devel/tradcpp all the time, so that when buidling with clang we do not depend on gcc's cpp.
Make imake respect CC and CXX
Make imake respect USE_GCC (if set imake will use gcc's cpp).
While here:
- Remove a couple of indefinite articles from comments
- Trim headers
- Fix a couple of ports to build with clang or use: USE_GCC=any
- Fix a now useless redefinition of the extraction chain
- Fix a typo in japanese/Wnn7-lib bundled imake template definitions
- Fix some XMKMF execution with no env specified
- Use options helper in x11/xautolock to simplify the port
