Date: Sun, 7 Nov 2004 04:37:32 +0100 From: Michael Nottebrock <michaelnottebrock@gmx.net> To: freebsd-ports-bugs@freebsd.org, danny@ricin.com Subject: Re: ports/72156: [patch] Update x11-toolkits/py-kde to 3.11.3 and fix unfetchable Message-ID: <200411070437.36897.michaelnottebrock@gmx.net> In-Reply-To: <200411070322.26536.danny@ricin.com> References: <200411061606.iA6G6x3g026877@freefall.freebsd.org> <200411070322.26536.danny@ricin.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart22469503.MgA2dm8Bs3 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday, 7. November 2004 03:22, Danny Pansters wrote: > On Saturday 6 November 2004 17:06, you wrote: > > Unfortunately PyKDE 3.11.3 is known to not compile with > > KDE 3.3.1 (fix unknown), so the window of a working py- > > kde port will be very short. > > Woah. Wait a second here. Is there a kde-3.3.1 port yet? No there isn't. = So > this unfortunate fact lies on the kde@ maintainers' plate, before blaming > porters who target the kde@ current port version (3.3.0), no? I didn't ev= en > know this and it's not very reasonable to expect me to. I don't and I'm not blaming anyone, I'm just stating a fact to give anybody= =20 who cares a heads-up. > I know that py-kde has recently been put into kde's cvs but it's not going > into a regular kde package yet as far as I know. Moreover, the py-kde in kdebindings is outdated - it's not even at 3.11.3 y= et. > Most likely also not in=20 > 3.3.1. Probably more like 4.0. So for now it'll be stuck being an extra > port. kdebindings is very unlikely to ever become a port of its own anyway, so th= e=20 extra port is a good thing, too. > [rant snipped] Suffice to say you're getting this the completely wrong way. I'm glad someb= ody=20 actually cares for PyQT/KDE, I had pretty much given up hope on it. > Oh yeah, as implicated by the Makefile you committed, I indeed decline > maintainership on second thought. It's not needed. Very thoughtful to > anticipate on this on my behalf already. Of course by logic the same goes > for related ports py-sip and py-qt. I didn't implicate anything, I just committed the diff as you submitted it.= I=20 read the Description field wrong though, and as a consequence didn't read P= R=20 72153 and PR 72154, which I've reopened now(*). I'd be glad if you took=20 maintainership of the triple. (*) I was pointed to PR 72156 by the recent list of unfetchable ports poste= d=20 to ports@, that's why I got this whole thing somewhat out of sequence. I kn= ow=20 it must be frustrating to see the result of your hard work committed in a=20 seemingly careless fashion - my apologies. I'll try and get the other PRs=20 related sorted out now. =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 --nextPart22469503.MgA2dm8Bs3 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBjZiAXhc68WspdLARAqrNAJ9S6k2gJE1IquYURRXAPD8L53VamQCfcSeD c83jlf3lqGjzZHJkIDB2BW8= =vkLr -----END PGP SIGNATURE----- --nextPart22469503.MgA2dm8Bs3--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200411070437.36897.michaelnottebrock>