non port: net-im/qxmpp/Makefile |
Number of commits found: 21 |
Sunday, 11 Feb 2024
|
07:21 Jason E. Hale (jhale)
net-im/qxmpp: Update to 1.6.0
Update LICENSE - it's really LGPL21+
Remove wonderous use of USES=libtool alongside of USES=cmake. Still
trying to figure out how that ever came to pass.
Disable building of examples which we wern't installing anyways and make
PLIST_SUB more readable.
Add a TEST option to optionally build tests (previously on by default),
which eliminates ~274 targets for normal builds, but still lets us check
if everything is all hunky dory.
cca8f3b |
Monday, 5 Feb 2024
|
19:43 Adriaan de Groot (adridg)
net-im/qxmpp: update to 1.5.6, latest upstream
Release notes are at
https://github.com/qxmpp-project/qxmpp/releases/tag/v1.5.6
and mention improvements in encryption and some minor packaging changes.
While here, bump net-im/kaidan to get it to rebuild against new libs.
0687c64 |
Friday, 26 May 2023
|
10:06 Tobias C. Berner (tcberner)
net-im/qxmpp: flavorize for Qt5 and Qt6
17fcec7 |
Wednesday, 16 Jan 2019
|
11:13 tijl
Fix Qt5 symbol version scripts to put the catch-all clause first. When
a symbol matches multiple clauses the last one takes precedence. If the
catch-all is last it captures everything. In the case of Qt5 libraries
this caused all symbols to have a Qt_5 label while some should have
Qt_5_PRIVATE_API. This only affects lld because GNU ld always gives the
catch-all lowest priority.
Older versions of Qt5Webengine exported some memory allocation symbols from
the bundled Chromium. Version 5.9 stopped exporting these [1] but the
symbols were kept as weak wrappers for the standard allocation functions to
maintain binary compatibility. [2][3] The problem is that the call to the
standard function in these weak wrappers is only resolved to the standard
function if there's a call to this standard function in other parts of
Qt5Webengine, because only then is there a non-weak symbol that takes
precedence over the weak one. If there's no such non-weak symbol the call
in the weak wrapper resolves to the weak wrapper itself creating an infinite
call loop that overflows the stack and causes a crash. Some of the
allocation functions are variants of C++ new and delete and it probably
depends on the compiler whether these variants are used in other parts of
Qt5Webengine.
Remove the weak wrappers (make them Linux specific). This isn't binary
compatible but we are already breaking that with the changes to the symbol
versions.
[1]
https://github.com/qt/qtwebengine/commit/5c2cbfccf9aafb547b0b30914c4056abd25942a4
[2]
https://github.com/qt/qtwebengine/commit/2ed5054e3a800fa97c2c9e920ba1e6ea4b6ef2a5
[3]
https://github.com/qt/qtwebengine/commit/009f5ebb4bd6e50188671e0815a5dae6afe39db5
Bump all ports that depend on Qt5.
PR: 234070
Exp-run by: antoine
Approved by: kde (adridg)
|
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, 2 Dec 2018
|
15:41 rene
Mark QT4 ports/functionality for removal on 2019-03-15
While here, chase some KDE4 ports and functionality, these are scheduled for
removal on 2018-12-31. Change the default option/flavor to QT5 where applicable
or use alternative toolkits like GTK.
Submitted by: tcberner
Reviewed by: adridg, jhale, rene, tcberner
Approved by: portmgr (implicit, flavor hook)
Differential Revision: https://reviews.freebsd.org/D17741
|
Sunday, 28 Oct 2018
|
08:56 linimon
Fix build for -qt5 port on GCC-based architectures.
PR: 232094
Submitted by: Piotr Kubaj
|
Thursday, 28 Jun 2018
|
17:39 tcberner
Replace bsd.qt.mk by Uses/qt.mk and Uses/qt-dist.mk
From now on, ports that depend on Qt4 will have to set
USES= qt:4
USE_QT= foo bar
ports depending on Qt5 will use
USES= qt:5
USE_QT= foo bar
PR: 229225
Exp-run by: antoine
Reviewed by: mat
Approved by: portmgr (antoine)
Differential Revision: -https://reviews.freebsd.org/D15540
|
Friday, 23 Feb 2018
|
21:09 rene
Reset vg@'s ports after he resigned.
With hat: portmgr-secretary
|
Monday, 5 Dec 2016
|
20:26 pawel
Add qxmpp Qt5 slave port needed for polish/kadu update
PR: 214547
Submitted by: myself
Approved by: maintainer timeout
|
Tuesday, 1 Mar 2016
|
21:10 pawel
- Update to version 0.9.3
- Add LICENSE_FILE
- Use PLIST_SUB to parametrize lib version in pkg-plist
- Disable port's self checks by QMAKE_ARGS because they
fail to compile with clang 3.7.1 on 11-CURRENT
PR: 207169
Submitted by: myself
Approved by: maintainer timeout
|
Thursday, 7 May 2015
|
17:26 mat
Update ports in the n* categories to not use GH_COMMIT.
With minor cleanups to make things simpler.
With hat: portmgr
Sponsored by: Absolight
|
Thursday, 19 Mar 2015
|
16:44 bdrewery
Update USE_GITHUB so it does not require GH_COMMIT.
Using this new scheme allows only setting the _tag_ or _commit hash_ in
GH_TAGNAME and not having to know the hash for a tag. This scheme will
download a tarball that has a different checksum than before due to a changed
directory name for extraction.
The following MASTER_SITES are provided to retain the old checksum and
directory structure (that require GH_COMMIT):
GH -> GHL
GITHUB -> GITHUB_LEGACY
Differential Revision: https://reviews.freebsd.org/D748
Submitted by: amdmi3
Reviewed by: mat, swills, antoine, bdrewery
With hat: portmgr
|
Saturday, 20 Dec 2014
|
18:30 antoine
Use GH_COMMIT
|
Tuesday, 8 Jul 2014
|
22:03 vg
- Bump version
- Update to 0.8.0
- Moved qxmpp-leechcraft because merged into qxmpp
|
Friday, 22 Nov 2013
|
12:55 makc
- Convert to USES=qmake (and other USES while I'm here)
- Add state support
- Convert LIB_DEPENDS to new style, adjust USE_QT4 components, etc.
Approved by: portmgr (blanket approval)
|
Friday, 20 Sep 2013
|
22:13 bapt
Add NO_STAGE all over the place in preparation for the staging support (cat:
net-im)
|
Monday, 22 Jul 2013
|
14:34 vg
- Changed my email
- Trim Makefile headers and positions name and surname within
Approved by: eadler, rm (mentors)
|
Wednesday, 6 Jun 2012
|
06:44 miwi
- Convert USE_QT_VER=4 and QT_COMPONETS to USE_QT4
Review by: bapt, David Naylor (kde team)
|
Friday, 1 Jun 2012
|
05:26 dinoex
- update png to 1.5.10
|
Wednesday, 11 Jan 2012
|
19:54 pawel
QXmpp is pretty intuitive and easy to use. It uses Qt extensively.
Qt is the only third party library it is dependent on. Users need
to a have working knowledge of C++ and Qt basics (Signals and Slots
and Qt data types). The underlying TCP socket and the XMPP RFCs
(RFC3920 and RFC3921) have been encapsulated into classes and
functions. Therefore the user would not be bothered with these
details. But it is always recommended to the advanced users to read
and enjoy the low level details.
WWW: http://code.google.com/p/qxmpp/
PR: ports/163967
Submitted by: Gvozdikov Veniamin <g.veniamin@googlemail.com>
|
Number of commits found: 21 |