From owner-freebsd-x11@FreeBSD.ORG Fri Jul 4 23:15:55 2014 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 34E79E4C; Fri, 4 Jul 2014 23:15:55 +0000 (UTC) Received: from astart2.astart.com (108-248-95-193.lightspeed.sndgca.sbcglobal.net [108.248.95.193]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DDC142CFE; Fri, 4 Jul 2014 23:15:54 +0000 (UTC) Received: from laptop_84.private (localhost [127.0.0.1]) by astart2.astart.com (8.14.4/8.14.4) with ESMTP id s64NFpwM059075; Fri, 4 Jul 2014 16:15:52 -0700 (PDT) (envelope-from papowell@astart.com) Message-ID: <53B735A6.7090803@astart.com> Date: Fri, 04 Jul 2014 16:15:50 -0700 From: Patrick Powell Reply-To: papowell@astart.com Organization: Astart Technologies User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130714 Thunderbird/17.0.7 MIME-Version: 1.0 To: Koop Mast Subject: Re: kde4 packages, WITHOUT_NEW_XORG fails References: <53B6D2CE.1090604@astart.com> <53B6FA75.6020302@astart.com> <53B71B56.5070009@rainbow-runner.nl> In-Reply-To: <53B71B56.5070009@rainbow-runner.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kevin Oberman , "freebsd-x11@freebsd.org" , FreeBSD Ports ML X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2014 23:15:55 -0000 On 07/04/14 14:23, Koop Mast wrote: > On 4-7-2014 22:49, Kevin Oberman wrote: >> On Fri, Jul 4, 2014 at 12:03 PM, Patrick Powell >> wrote: >> >>> On 07/04/14 09:56, Kevin Oberman wrote: >>> >>> On Fri, Jul 4, 2014 at 9:14 AM, Patrick Powell >>> 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@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@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. > ports/UPDATING states: > 20140218: > AFFECTS: users of KDE SC 4 > AUTHOR: kde@FreeBSD.org > > KDE SC ports have been updated to 4.12.2. kdeadmin, kdenetwork, kdesdk, > and kdetoys ports have been split due to upstream changes. > > KDE Workspace port has been updated to 4.11.6. It requires modern > Mesa libraries, provided by WITH_NEW_XORG knob. To update Xorg ports > to newer version follow instructions at > https://wiki.freebsd.org/Graphics > > So it not possible anymore to run KDE4 with WITHOUT_NEW_XORG. > > -Koop > Ahhh!!! I missed that. If this is the case, then perhaps the default for generating the PKGNG repository should be WITH_NEW_XORG? Then we could use the PKGNG respository for KDE4 applications. OR: we could have two repositories: one which uses WITHOUT_NEW_XORG and has the old Xorg drivers and no KDE4 support and one with WITH_NEW_XORG which has the new Xorg drivers and KDE4 support. I think I read some discussion about this possibility but I can't recall the outcome.