Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 May 2007 17:00:24 +0200
From:      Michael Nottebrock <lofi@freebsd.org>
To:        Mikhail Teterin <mi+kde@aldan.algebra.com>
Cc:        x11@freebsd.org, kde@freebsd.org, Kris Kennaway <kris@obsecurity.org>
Subject:   Re: [kde-freebsd] qt assumes /usr/X11R6
Message-ID:  <200705081700.25645.lofi@freebsd.org>
In-Reply-To: <200705062004.28475@aldan>
References:  <20070505163649.GA61199@xor.obsecurity.org> <200705061816.52049.lofi@freebsd.org> <200705062004.28475@aldan>

next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1581553.tZuJnLyKBq
Content-Type: text/plain;
  charset="koi8-u"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Monday, 7. May 2007, Mikhail Teterin wrote:
> On Sunday 06 May 2007 12:16, Michael Nottebrock wrote:
> =3D > Actually qmake just needs a version bump, it correctly patches
> =3D > /usr/X11R6 to ${X11BASE} (except for the freebsd-g++34 script which=
 we
> =3D > dont seem to use), so it needs to redo this now that X11BASE is
> =3D > changing. =9Aflz has bumped this in git. =9AI am hoping we don't ne=
ed to
> =3D > also bump everything that uses qmake since nothing copies this
> =3D > definition into its own files (which is the issue with .la files)
> =3D
> =3D Just bumping qmake should be fine, yes.
>
> Does not this mean bumping it for ALL x11-ports?

As I understand it, the update script for the X11R7 import will forcibly=20
update all ports with a dependency on X. Qmake technically doesn't depend o=
n=20
the X libraries, but it does generate the initial configuration for Qt, whi=
ch=20
does depend on the X libs, thus it needs to be rebuilt, but isn't=20
automatically caught by the script.

> Frankly, I find it to be a design flaw, that a change outside a port
> requires version/revision bumps of the port itself...

You can look at it that way, but the real flaw is in qmake/Qt then - the=20
mkspecs definitions are really a lame shortcut Trolltech took instead of=20
writing proper configure scripts. Hardwiring paths in there isn't even the=
=20
worst thing they do IMHO, the hardwiring of C(XX)FLAGS causes much more=20
confusion.

> Michael, if you are convinced, the bump is needed, please, do the honors.=
=2E.

I think it will be done for us once the X11R7 import happens.


Cheers,
=2D-=20
   ,_,   | Michael Nottebrock               | lofi@freebsd.org
 (/^ ^\) | FreeBSD - The Power to Serve     | http://www.freebsd.org
   \u/   | K Desktop Environment on FreeBSD | http://freebsd.kde.org

--nextPart1581553.tZuJnLyKBq
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)

iD8DBQBGQJCJXhc68WspdLARAkLXAJ4+sgn9JlWfUmu3DXNY7PhilrnzWwCeJkiJ
O7LlSXdOjqBfpWRfJkeAnrs=
=CvAN
-----END PGP SIGNATURE-----

--nextPart1581553.tZuJnLyKBq--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200705081700.25645.lofi>