From owner-freebsd-ports@freebsd.org Thu Dec 21 09:19:19 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09769E88DAE for ; Thu, 21 Dec 2017 09:19:19 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mail.madpilot.net (grunt.madpilot.net [78.47.145.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B576C7E950 for ; Thu, 21 Dec 2017 09:19:18 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3z2R0Z2YPkzb4K; Thu, 21 Dec 2017 10:19:10 +0100 (CET) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10024) with ESMTP id hLoDPXt4teUe; Thu, 21 Dec 2017 10:19:04 +0100 (CET) Received: from marvin.madpilot.net (micro.madpilot.net [88.149.173.206]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.madpilot.net (Postfix) with ESMTPSA; Thu, 21 Dec 2017 10:19:04 +0100 (CET) Subject: Re: Vote: making wayland=on default To: Niclas Zeising , freebsd-ports@freebsd.org References: From: Guido Falsi Message-ID: <34f699e2-b852-63fd-f6d6-a862a42569de@FreeBSD.org> Date: Thu, 21 Dec 2017 10:19:03 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Dec 2017 09:19:19 -0000 On 12/20/2017 21:47, Niclas Zeising wrote: > On 12/20/17 10:20, Johannes Lundberg wrote: >> Hi >> >> I want to suggest that we enable wayland by default. In current state >> having some parts of wayland in ports is basically useless the >> end-users themselves re-build gtk30 and mesa-libs with wayland >> enabled. >> >> libwayland-egl.so from mesa-libs and the extra libraries and headers >> from gtk30 adds like a few KB, a drop in the ocean compared to xorg >> packages. (might be something more that I missed) >> >> Personally I see no reason not to make it default on, even with >> flavors coming up. For any Desktop user (as well as embedded devices >> like IVI-systems and whatnot), Wayland is the future. There's no >> escaping that. >> >> Wayland has been quite usable on FreeBSD for over a year now but >> access to it is limited due to the extra efforts required to use it. >> >> If we are to compare with the other guys, several Linux distros are >> already switching to wayland-based compositors as default window >> server. >> >> What do you think? >> > > > With my x11@ hat on. > > I have no problem with this, as long as the old xorg stuff keeps on > working, as you've stated they will do.  I do not have time to fix this > this week, but if you can help me prepare a patch we can perhaps get it > in after that (beginning of next week, in the days between Christmas and > new years).  Do you know which ports are affected by this, and have a > WAYLAND option?  We should also check, probably just in case, if portmgr > thinks an exp run is needed (I don't think so). > I recently added a WAYLAND option to the multimedia/libva port I maintain. I set it to off by default but that can be changes without problems. -- Guido Falsi