Date: Sun, 12 Jan 2003 10:18:30 -0800 From: Marcel Moolenaar <marcel@xcllnt.net> To: AlanE <alane@geeksrus.net> Cc: Andy Fawcett <andy@athame.co.uk>, Kris Kennaway <kris@citusc.usc.edu>, Kris Kennaway <kris@obsecurity.org>, kde@FreeBSD.ORG, alpha@FreeBSD.ORG, Terry Lambert <tlambert2@mindspring.com> Subject: Re: [kde-freebsd] koffice broken on alpha Message-ID: <20030112181830.GA616@dhcp01.pn.xcllnt.net> In-Reply-To: <20030112134129.GA11765@wwweasel.geeksrus.net> References: <20030104032551.A899@citusc.usc.edu> <200301120315.40618.andy@athame.co.uk> <20030112013223.GA2057@wwweasel.geeksrus.net> <200301121302.22191.andy@athame.co.uk> <20030112134129.GA11765@wwweasel.geeksrus.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 12, 2003 at 08:41:29AM -0500, AlanE wrote: > > > >Anyway, this would now appear to be academic, since Kris's last mail > >states that the recent KOffice update in ports has screwed any chance > >of updating it and retagging. > > That's my misunderstanding of his wishes. Sorry for hassle it is now > causing. I didn't read it as "don't touch", I read it as what it said, > "no sweeping changes like KDE or Gnome". And I didn't think of the > possible implications of just updating koffice. > > The question is, what do we do now? We can always back-out the koffice upgrade, apply the patch to the old version, slide the tag and immediately upgrade koffice again to the version it now is. It only causes some repo bloat and some additional work. Note that the intermediate state can be broken (ie you don't back-out dependent changes to other ports), so the time frame in which this is done should be kept small... Just a thought, -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030112181830.GA616>