A bunch of ports commits at the end of August marked all the KDE4 ports that
kde@ is responsible for, as DEPRECATED, e.g. for x11/kdelibs-kde4/
r478483 | adridg | 2018-08-30 20:40:36 +0200 (Thu, 30 Aug 2018) | 10 lines
Deprecate KDE4 software, categories www-x11-themes
Since not everyone reads t
On Wednesday, 14 November 2018 22:05:38 CET freebsd-ports-requ...@freebsd.org
wrote:
> Date: Wed, 14 Nov 2018 21:00:20 +0900
> From: KIRIYAMA Kazuhiko
> To: freebsd-ports@freebsd.org
> Cc: k...@kx.openedu.org
> Subject: multimedia/umplayer build failed (13.0-CURRENT/r339677)
> Message-ID: <201811
On Monday, 24 December 2018 13:00:02 CET freebsd-ports-requ...@freebsd.org
wrote:
> > The qt* ports spreads around in the whole portstree.
> >
> > It is reasonable to concentrate all these ports in a qt category? I
> > think it is easier to find (and also easier to maintain).
>
> Indeed it is a
On Monday, 24 December 2018 18:14:51 CET Michael Butler wrote:
> As follows:
.. and here I had tested on 11.2 with base SSL, openssl, openssl111, .. and
not considered that 12.0 would remove the definition of IFM_FDDI entirely.
Fixed, I hope, in r488281 (which built for me in a 12.0-RC3 VM).
[a
Niclas wrote:
On Thursday, 3 January 2019 13:00:02 CET freebsd-ports-requ...@freebsd.org
wrote:
> > Firefox and Chromium both depend on GTK3, so it's highly likely that a
> > typical desktop user has GTK3 installed.
>
> +1, GTK3 is probably the best choice.
>
> As a side note, it looks like lib
On Tuesday, 15 January 2019 13:00:02 CET freebsd-ports-requ...@freebsd.org
wrote:
> While I can't go through all of them, but qr5-qdoc builds fine with llvm70,
> though I can't promise that it will work. I suspect that the port just
> needs updating to allow either port.
Yes, kde@ wants to update
On Friday, 18 January 2019 13:01:37 CET freebsd-ports-requ...@freebsd.org
wrote:
> Since mesa uses llvm libraries (not just toolchain to build) this can
> not be made in to a build time only dependency.
>
> There is some more information on this issue here:
> https://wiki.freebsd.org/WhyDoIHaveTo
On Saturday, February 9, 2019 1:00:02 PM CET freebsd-ports-requ...@freebsd.org
wrote:
> From: Torfinn Ingolfsen
> To: FreeBSD Ports ML
> Subject: FreeCAD 0.17 - is anyone using it?
> Message-ID:
>
> Content-Type: text/plain; charset="UTF-8"
>
> Just checking: is anyone using FreeCAD 0.
On Monday, 11 March 2019 13:01:43 CET freebsd-ports-requ...@freebsd.org wrote:
> ../qbearerengine_impl.h:48:1: error: expected class-name before '{' token
I *imagine* (since I don't have anything that can try to reproduce this build
sensibly) that you're hitting a case where QT_NO_BEARERMANAGEMEN
On Monday, 3 June 2019 14:00:01 CEST freebsd-ports-requ...@freebsd.org wrote:
> From: Gary Aitken
>
> I'm trying to port some linux code which uses cmake, and clearly don't
> know what I'm doing.
>
> I have
>USES= cmake
> set, but a
>make build
> terminates with:
>cd: /usr/ports/cad
On Friday, 28 June 2019 14:00:01 CEST freebsd-ports-requ...@freebsd.org wrote:
> [FreeBSD 11.3-PRERELEASE #1 r349440 amd64 / ports at r505184]
>
> Getting a compilation error when build ports/textproc/qt5-xmlpatterns
>
> I'm doing a 'portmaster -a' but a
> 'cd /usr/ports/textproc/qt5-xmlpatterns
On Sunday, 30 June 2019 22:19:33 CEST Andy Farkas wrote:
> On 29/06/2019 05:29, Adriaan de Groot wrote:
> > On Friday, 28 June 2019 14:00:01 CEST freebsd-ports-requ...@freebsd.org
wrote:
> >> [FreeBSD 11.3-PRERELEASE #1 r349440 amd64 / ports at r505184]
> >>
> >&
On Sunday, 18 August 2019 14:00:01 CEST freebsd-ports-requ...@freebsd.org
wrote:
> > So I hoped to collect experiences on this.
>
> I was favorably impressed by Otter Browser, but have not been able to update
> because my FreeBSD installation, 11.1-STABLE, is too far behind for
> updating ports.
On Thursday, 10 October 2019 14:05:56 CEST freebsd-ports-requ...@freebsd.org
wrote:
> > I've run into the same error just yesterday. As a workaround, deinstall
> > the devel/evdev-proto port (it's not the libmtdev port which is the
> > problem) and it will use the base-system evdev includes.
> >
Responding specifically to falkon, not to pkg-meta-issue.
On Tuesday, 15 October 2019 14:00:02 CEST freebsd-ports-requ...@freebsd.org
wrote:
> Today I wanted to reinstall falkon (due to some library updates,
> related to other packages on my system).
>
> root@kg-core2# pkg install -f falkon
> Up
On Thursday, December 5, 2019 5:22:39 PM CET Carmel NY wrote:
> I have Samba Version 4.10.10 installed. When attempting to build
> devel/kio-extras with the:
>
> SAMBA=on: Needed to build the SMB kioslave
>
> which is the default setting in the port, the build fails with the
> message that the w
On 2020 febula d. 24id 13:00:05 CET freebsd-ports-requ...@freebsd.org wrote:
> Date: Mon, 24 Feb 2020 12:48:11 +0100
> From: Miroslav Lachman <000.f...@quip.cz>
> To: freebsd-ports@freebsd.org
> Subject: Cannot build qt5-webkit with debug
> Message-ID:
> Content-Type: text/plain; charset=UTF-8; fo
On Friday, 3 April 2020 14:00:11 CEST freebsd-ports-requ...@freebsd.org wrote:
> Message: 1
> Date: Fri, 3 Apr 2020 08:44:14 +0200 (CEST)
> From: Wojciech Puchar
> To: freebsd-ports@freebsd.org
> Subject: qrc:/Desktop.qml:26 module "QtQuick.Dialogs" is not installed
> Message-ID:
> Content-Type:
On Saturday, 4 April 2020 14:00:14 CEST freebsd-ports-requ...@freebsd.org
wrote:
> Message: 8
> Date: Fri, 3 Apr 2020 21:58:29 +0200 (CEST)
> From: Wojciech Puchar
> Subject: Re: qrc:/Desktop.qml:26 module "QtQuick.Dialogs" is not
> installed
If this is about net-im/ruqola, then kde@ (in
Qt ports are annoying like that; it's an incompatibility between pre-5.14 and
(current) 5.14 where it picks up the wrong CMake support bits. Uninstall Qt <
5.14, then build Qt 5.14. Or use poudriere, which builds in a clean
environment.
[ade]
signature.asc
Description: This is a digitally sign
On Thursday, 16 April 2020 00:05:02 CEST The Doctor wrote:
> On Wed, Apr 15, 2020 at 09:20:17PM +0200, Adriaan de Groot wrote:
> > Qt ports are annoying like that; it's an incompatibility between pre-5.14
> > and (current) 5.14 where it picks up the wrong CMake support bi
On Wednesday, 13 May 2020 14:00:02 CEST freebsd-ports-requ...@freebsd.org
wrote:
> Just found the tip pf the iceberg.
Gentoo kindly pointed me to a good explanation:
https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-qt/qtcore/files/
qtcore-5.14.1-cmake-macro-backward-compat.patch
That's a patc
On Thursday, 2 July 2020 14:00:01 CEST freebsd-ports-requ...@freebsd.org
wrote:
>1. audoi/openal-soft fails (Andy Farkas)
>
>
> # portmaster audio/openal-soft
>
What you're showing here are a couple of *warnings* from CMake (known issues,
not harmful: recent CMake is more picky about nami
The Chromium build system -- and as a consequence, also QtWebEngine -- still
uses Python 2.7. This is going to be a real problem about six months down the
line, and I have no idea how upstream is going to deal with it. I've heard
there are patches buried deep within the chocolate factory, but no
I'm wondering about libusb, because the libusb in base is missing a bunch of
"current" API, and the API version number doesn't match Linux (upstream?) idea
of what was available in historical versions.
tl;dr: would a libusb port make any sense? Is updating libusb in base
feasible?
Background:
On Sunday, 16 August 2020 14:00:01 CEST freebsd-ports-requ...@freebsd.org
wrote:
> Message: 10
> Date: Sun, 16 Aug 2020 13:53:21 +0200
> From: Christoph Moench-Tegeder
>
> ## Carmel (carmel...@outlook.com):
> > I would have expected to see something in"UPDATING". The only mention
> > is in "MOVE
On Monday, 4 January 2021 04:22:32 CET Li-Wen Hsu wrote:
> On Mon, Jan 4, 2021 at 9:42 AM Nick Wolff wrote:
> > Hello Adriaan ,
> >
> > https://svnweb.freebsd.org/ports?view=revision&revision=560251 Seems to
> > cause poudriere to puke due to a missing line in graphics/Makefile for new
> > port
On Saturday, 20 March 2021 04:42:32 CET Alex V. Petrov wrote:
> ===>>> Update for kf5-kparts-5.79.0 failed
> ===>>> Aborting update
Looks like you're trying to install in a dirty (previous version is installed)
system. Please don't do that.
The log isn't all that useful: it looks like the buil
On Thursday, 25 March 2021 13:00:02 CET freebsd-ports-requ...@freebsd.org
wrote:
> The idea is to try to have www/qt5-webengine fixed before the expiration
> time, saving with it a bunch of innocent ports depending on it, correct?
In the sense of "have one guy take a stab at it over the weekend b
As prep-work for CMake updates I locally "exp-run" all the ports that use
CMake. I use poudriere for this, with the `-t` flag to test each port.
dns/knot-resolver fails to package like that, with this error:
===
===> Building package for knot-reso
I build many ports in poudriere with the `-t` (test port) flag. Ports that use
Python-based tools tend to fail with a fs_violation. For instance, FreeCAD:
=>> Checking for filesystem violations... done
=>> Error: Filesystem touched during build:
extra: usr/local/lib/python3.7/site-packages/shibok
On Sunday, 18 April 2021 14:00:01 CEST freebsd-ports-requ...@freebsd.org
wrote:
> >> So perhaps that is the best way to avoid having to deal with ABI/API
> >> breakage...
> >> After that it is up to the maintainers of the dependant packages to
> >> update their package and start using boost-1.75.
On Tuesday, 27 April 2021 11:23:51 CEST freebsd-ports-requ...@freebsd.org
wrote:
> From: Simon Wright
> To: freebsd-ports@freebsd.org
> Subject: Bug 242248 - misc/compat11x pkg-descr correction [PATCH],
> committer love pls!
> Message-ID: <6c276940-b0e4-28f6-8bb3-c373b3642...@gmx.net>
> C
On Friday, January 04, 2013 07:24:28 PM Jerry wrote:
> Following the directions in UPDATING, I used the following command:
>
> portupgrade -fr devel/libical
>
> That port updated correctly; however, the next port:
> The entire build log is available here:
>
> https://www.seibercom.n
[where did this discussion take place, earlier? this is the first I've seen it
-- oh, the ports@ list]
So, there are roughly two migration paths: supposing someone has x11/kde4
installed, which has dependencies on many applications and a Plasma 4 desktop,
kde@ wants (wanted) to make it possible
35 matches
Mail list logo
