NEW_XORG and vt(4) in stable branches

[Raphael Kubo da Costa]

John Baldwin <jhb at freebsd.org> 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.