From owner-freebsd-x11@FreeBSD.ORG Wed Feb 12 22:24:28 2014 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C9409DDA; Wed, 12 Feb 2014 22:24:28 +0000 (UTC) Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8E66615C2; Wed, 12 Feb 2014 22:24:27 +0000 (UTC) Received: by mail-lb0-f176.google.com with SMTP id w7so7497920lbi.21 for ; Wed, 12 Feb 2014 14:24:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=QvXaJ3UB/UzSiq5OwMy1dK2PsqqLirUzlHrbTP9Q6Wc=; b=mLpAEvWSYRaQazNQscSXz0T3repTpOY/buFW9OnVj3jMgoht1J8cgfSl0PRg2z7uWk eWYwcxbaLQ/OAh+2JEkhcSXNhJyEQVYD77koivpeFkf4iYeHYd888lvyLKuMsti+x1mD vpLLxGAxIFYLdiLoVRWvvlc54x6Wb1bycHrcg2ClZ2fous/HL6FXHuTSdgH9Y+A6p5HE ouYAxJF5445YuMifMwpLWOMf/jP0ugw0zZJFIR7Ux1d765pexvSasXToRkpvF/Sm/I5j ejZdusqLjw3lUP8m1zUKP3xhqsBNTSzv6cz4LKwO5JGRf61FYkgcx8dEsO2poTmOnT+b 8k7A== X-Received: by 10.152.209.7 with SMTP id mi7mr3707058lac.42.1392243865492; Wed, 12 Feb 2014 14:24:25 -0800 (PST) Received: from orwell.Elisa.gmail.com (a91-154-115-217.elisa-laajakaista.fi. [91.154.115.217]) by mx.google.com with ESMTPSA id dm8sm35386410lad.7.2014.02.12.14.24.23 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 12 Feb 2014 14:24:24 -0800 (PST) Sender: Raphael Kubo da Costa From: Raphael Kubo da Costa To: John Baldwin Subject: Re: NEW_XORG and vt(4) in stable branches References: <201402121443.44313.jhb@freebsd.org> Date: Thu, 13 Feb 2014 00:24:15 +0200 In-Reply-To: <201402121443.44313.jhb@freebsd.org> (John Baldwin's message of "Wed, 12 Feb 2014 14:43:44 -0500") Message-ID: <86r478rmuo.fsf@orwell.Elisa> User-Agent: Gnus/5.13001 (Ma Gnus v0.10) Emacs/24.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain Cc: ray@freebsd.org, x11@freebsd.org, FreeBSD Core Team X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Feb 2014 22:24:28 -0000 John Baldwin writes: > Our current feeling is that we would like to not enable NEW_XORG by default > for the packages for a given src branch until vt(4) has been merged to that > branch. We do not think that vt(4) needs to be enabled by default in the > branch; just having it available as an option as it is in HEAD would be > sufficient. Our understanding is that merging vt(4) in its current-ish form > to stable/10 and stable/9 is quite feasible and not a major nightmare. We do > not feel that it is necessary to merge to stable/8 as drm2 isn't merged to > stable/8 either. (Our assumption is that stable/8 will just stay with the old > Xorg and the ports tree will have to support old Xorg until 8.x support in > ports is EOL'd.) I'd just like to add another data point with my kde@ hat: we're about to update the KDE ports in the tree to 4.12.2, and since the 4.11 series x11/kde4-workspaces requires NEW_XORG to build (it uses symbols which are not present in the Mesa version used with WITH_NEW_XORG=no). This means there are not going to be any packages for kde4-workspace (and ports that depend on it) until WITH_NEW_XORG defaults to "on" in the 9 and 10 in the pkg cluster, and "pkg install kde" will not work unless people are using -HEAD. So for us, the sooner vt(4) gets merged into 9 and 10, the better, and I guess people on 8 who only use binary packages will not have much choice but to build some ports with WITH_NEW_XORG themselves.