From nobody Mon Nov 22 23:06:23 2021 X-Original-To: ports-bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id C02F51888B9B for ; Mon, 22 Nov 2021 23:06:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HyjZ74zdpz3Fxp for ; Mon, 22 Nov 2021 23:06:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 88CFE30C6 for ; Mon, 22 Nov 2021 23:06:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 1AMN6NwE016098 for ; Mon, 22 Nov 2021 23:06:23 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 1AMN6NNe016097 for ports-bugs@FreeBSD.org; Mon, 22 Nov 2021 23:06:23 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 251117] [NEW PORT] www/palemoon: Open-source web browser Date: Mon, 22 Nov 2021 23:06:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: feature, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: olivier.freebsd@free.fr X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Ports bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-ports-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports-bugs@freebsd.org X-BeenThere: freebsd-ports-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251117 --- Comment #62 from Olivier Certner --- Hi Kubilay, Thanks for popping in. To first answer your questions: 1. The latest patch for 29.4.2.1 is indeed upstream's latest version. 2. QA: Makefile linted long ago, I've re-run portlint and I'll make a few m= inor fixes to the Makefile. As for builds, there have not been recent poudriere builds on FreeBSD infrastructure that I know of. Is it possible to request some? About tier-1 architectures, aarch64 is not supported. The port builds on am= d64 and i386, but for the latter I don't think it is possible to build on a real i386 machine, an amd64 box with 32-bit libs is probably necessary (linking should take more than 4GB per ld process). Recently, I've only built on 12-STABLE myself. Very recent reports by users above indicate some failure on CURRENT, which is likely to manifest itself = on 13-STABLE as well (after the last LLVM/clang update this summer). I have ve= ry little time currently, I plan to build on 13-STABLE myself soon, but if som= eone wants to help, he's welcome. 3. GCC is a mandatory requirement, because this is only what upstream suppo= rts and the only thing that currently works. Also, we'll lose official branding= if we don't use it. At start, I tried to get Palemoon working with LLVM/clang++, but the produc= ed binaries simply crashed, and light investigations did not reveal anything obvious. I don't precisely remember now, and I don't know the actual amount= of work it would take. Anyway, I simply don't have the time currently and it's= a priori unlikely that upstream will accept the eventual patches to build with LLVM/clang (when I brought the subject on the table months ago, I was very strongly told not to do it). As for bundled libs, I explained several times above why we cannot get away with ports dependencies (API changes notably). This is a hard requirement (I don't want/can't maintain a fork). There is also the licensing concern (long discussion above in this PR, in particular with bapt@). We can set RESTRICTED to solve it for now. In a discussion with upstream during summer, they stated they wanted most FreeBSD changes integrated into their codebase and build system, or they'll lose interest, and possibly remove all BSD-related compatibility code. So t= he long term fate of this port is mostly dependent on this process, which I probably won't start before end of this year. So, pushing a port before that appears to me as premature. --=20 You are receiving this mail because: You are the assignee for the bug.=