From owner-svn-ports-head@freebsd.org Wed Jan 23 06:25:43 2019 Return-Path: Delivered-To: svn-ports-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E01CB14BCAED; Wed, 23 Jan 2019 06:25:43 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 84E878C7DB; Wed, 23 Jan 2019 06:25:43 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 7692212DD; Wed, 23 Jan 2019 06:25:43 +0000 (UTC) From: Jan Beich To: Alexey Dokuchaev Cc: Martin Wilke , Christoph Moench-Tegeder , svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r490910 - in head: Mk Mk/Uses mail/thunderbird www/firefox www/firefox-esr www/firefox-i18n www/firefox/files www/palemoon www/seamonkey References: <201901212303.x0LN3jR3059519@repo.freebsd.org> <20190122100911.GA77378@elch.exwg.net> <20190122205210.GA2480@elch.exwg.net> <20190123021742.crxjjzlcvg3ly55k@miwitb.miwi.cc> <20190123044522.GA8128@FreeBSD.org> <20190123060910.GA74821@FreeBSD.org> Date: Wed, 23 Jan 2019 07:25:38 +0100 In-Reply-To: <20190123060910.GA74821@FreeBSD.org> (Alexey Dokuchaev's message of "Wed, 23 Jan 2019 06:09:10 +0000") Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Rspamd-Queue-Id: 84E878C7DB X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.82 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.99)[-0.990,0]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; NEURAL_HAM_SHORT(-0.83)[-0.832,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US] X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2019 06:25:44 -0000 Alexey Dokuchaev writes: > On Wed, Jan 23, 2019 at 06:52:09AM +0100, Jan Beich wrote: > >> Alexey Dokuchaev writes: >> > On Wed, Jan 23, 2019 at 10:17:42AM +0800, Martin Wilke wrote: >> >> On Tue, Jan 22, 2019 at 09:52:11PM +0100, Christoph Moench-Tegeder wrote: >> >> > ... >> >> > Given that WAYLAND is the default for us, and "without wayland" >> >> > might be untested anyways - would it make sense to remove the >> >> > WAYLAND option and force it to "on" always? >> > >> > Please don't. I have zero reasons to want/enable Wayland bits and deal >> > with all the extra bloat that comes with it. Modern FreeBSD/X.org stack >> > is quite bloated already (e.g. compared with my 8.4-STABLE setup). >> >> And I have zero reasons to fight your WAYLAND=off battle. If all you >> can offer are bikesheds then like with PulseAudio expect me to not care. > > While both Wayland and PulseAudio are of course useless pieces of software, > I did not object Wayland being enabled by default as long as I can turn it > off. I don't see how this level of granularity is bikeshed. There are > large parts of functionality that are completely useless for various groups > of people (graphics support for servers, CUPS support for users without a > printer, etc.) and thus were traditionally made optional. Pulling Wayland > unconditionally goes against the way we do things (and did for years) in > FreeBSD Ports Collection. If Firefox upstream drops support for building WAYLAND=off then I'm not going to spend extra effort to keep it alive.