kde4 packages, WITHOUT_NEW_XORG fails

[Kevin Oberman]

On Fri, Jul 4, 2014 at 12:03 PM, Patrick Powell <papowell at astart.com> wrote:

>  On 07/04/14 09:56, Kevin Oberman wrote:
>
> On Fri, Jul 4, 2014 at 9:14 AM, Patrick Powell <papowell at astart.com>
> wrote:
>
>> I have run into a problem trying to recompile the KDE4 packages with
>> WITHOUT_NEW_XORG=YES.
>>
>> >From the CHANGES file:
>> 20140416:
>>   AFFECTS: users of x11/xorg graphics/dri graphics/libGL and related ports
>>   AUTHOR: x11 at FreeBSD.org
>>
>>   The default xorg version has been switched on FreeBSD 10-STABLE and
>>   FreeBSD 9-STABLE.
>>
>>   To upgrade graphics/libGL, graphics/dri and related MESA ports, it is
>>   necessary to first remove the old versions of those ports.
>>   No special upgrade procedure is needed for xorg ports but it is
>>   necessary to recompile all xorg drivers (xf86-*) and other ports that
>>   depend on the xserver version, including
>>   emulators/virtualbox-ose-additions.  Portrevisions have been bumped
>>   where needed, but users of drivers not in the ports tree will need to
>>   recompile those.
>>
>>   If it is important to stay on the old versions, it is possible to
>>   specify WITHOUT_NEW_XORG= in /etc/make.conf to get the old xorg
>>   distribution.
>>
>>
>> My make.conf file:
>>   WITH_PKGNG=yes
>>   WITHOUT_NEW_XORG=yes
>>
>> I did portsnap fetch update, and then did:
>>
>> #> cd /usr/ports/x11/kde4
>> #> make missing >/tmp/missing_files
>>
>> I massaged the /tmp/missing_files to use pkg to try to download
>> a package if it was in the repository.  If they were not, I then
>> tried to use 'make BATCH=YES install' to compile and install the port.
>>
>>
>  Unfortunately,  many ports have been updated with calls to the Mesa API
> that do not exist in the WITHOUT_NEW_XORG version of Mesa. As a result, you
> can no longer build/run recent version of those ports WITHOUT_NEW_XORG. KDE
> is probably the bast known of these.
>
>  That leaves two options:
>  1. Move to the new Xorg versions (which may not support some older
> hardware)
>  2. Use an old (and possibly vulnerable) version of KDE
>
>  The Xorg and KDE folks simply don't provide any other options that I am
> aware of.
>  --
> R. Kevin Oberman, Network Engineer, Retired
> E-mail: rkoberman at gmail.com
>
> OK, then could they please update the CHANGES file and state that?  And/or
> put a warning in the UPDATING or CHANGES ports file:
>
> WITHOUT_NEW_XORG option not supported
>
> I appreciate the problems,  I was just hoping that there was a trivial
> solution to them...
>

I have no commit bit, but perhaps someone who does will put a note in
CHANGES. I certainly think it would be a good idea.

This discussion begs the question of why won't WITH_NEW_XORG work for you?
I am aware of some pretty old hardware that simply has no support in recent
Xorg servers, but these are pretty old by now. And, as time passes, the bit
rot will make more and more things fail with the old code.

I am far from an X expert, but a post to x11@ of the failure you see
WITH_NEW_XORG including the Xorg.0.log, /etc/make.conf, /etc/src.conf and
any Xorg.conf you are using might get things working (and might not). x11@
is a far better place to ask any of the questions about X issues.

I should also recommend that, if you have not already tried, move your
Xorg.conf aside and let X try to configure itself. It is very rare to
require a full configuration these days. Most only need things for added
fonts and extra modules. The xorg.conf on my laptop is only about 27 lines
long and mostly added fonts.
-- 
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkoberman at gmail.com