Date: Tue, 17 Apr 2007 20:23:37 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Michael Nottebrock <lofi@freebsd.org> Cc: freebsd-x11@freebsd.org, Andy Fawcett <andy@athame.co.uk>, kde@freebsd.org Subject: Re: [kde-freebsd] qt upgrade strangeness Message-ID: <20070418002337.GA8845@xor.obsecurity.org> In-Reply-To: <200704172058.53674.lofi@freebsd.org> References: <200704051229.27994.lists@jnielsen.net> <200704171633.59007.lofi@freebsd.org> <200704171638.39985.dejan.lesjak@ijs.si> <200704172058.53674.lofi@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 17, 2007 at 08:58:42PM +0200, Michael Nottebrock wrote: > > Would bumping revision of qmake and qt be enough or were you thinking of > > something more aggressive? >=20 > No - I'm guessing the problem is that qmake generates wrong dependencies = in=20 > Makefiles when it configures Qt with a prefix that is different from the = one=20 > of a previously installed Qt, with the dependencies being generated on fi= les=20 > in the destination install prefix instead of the workdir. The most obviou= s=20 > workaround: Deinstall (as in make deinstall) qt33, then (and only then)= =20 > rebuild and reinstall qt33 with the new PREFIX set. An update script coul= d=20 > take care of this rather easily as part of a post-update cleanup routine. >=20 > I can also try to reproduce this and, if I succeed, try to come up with s= ome=20 > post-configure in-place Makefile editing, if my guess turns out to be=20 > correct, but I am still busy with changing a number of qt4 ports to avoid= =20 > conflicting with qt33 after the X11BASE-move and flz@ already told me wou= ld=20 > very much like to remain on schedule and do the merge on the upcoming=20 > monday - I'm simply not sure I will be able to address this problem in ti= me. >=20 > Another option would be doing nothing, writing up an UPDATING entry and= =20 > pointing disgruntled users to that, of course. ;) I think having qt33 upgrade automatically (i.e. without requiring manual action) is a requirement for the xorg upgrade. We are currently also blocked on a portupgrade issue, but hopefully someone else will be able to fix qt in the next few days if you don't have the time. I would like to see a real solution instead of an upgrade script workaround (as mentioned no other ports are special-cased at this time because we have been able to find ways to avoid it). Kris --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGJWUIWry0BWjoQKURAt49AJ0X/G75SO00xXrFqnphYpd0KBvUXACgr6j4 JWoFxCFJOy4+CcVkB2J4sL4= =O8/Z -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070418002337.GA8845>