Date: Mon, 18 Mar 2002 21:57:43 +0100 From: Jochem Kossen <j.kossen@home.nl> To: Will Andrews <will@csociety.org> Cc: freebsd-xfree86@lists.csociety.org, ports@FreeBSD.ORG Subject: Re: HEADS UP: XFree86 4.2.0 going back in the tree Message-ID: <20020318205743.GA22186@jochem.dyndns.org> In-Reply-To: <20020318205343.GO53073@squall.waterspout.com> References: <20020318004547.GA62117@jochem.dyndns.org> <20020318015837.GV53073@squall.waterspout.com> <20020318192807.GA22036@jochem.dyndns.org> <20020318205343.GO53073@squall.waterspout.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 18, 2002 at 03:53:43PM -0500, Will Andrews wrote: > On Mon, Mar 18, 2002 at 08:28:07PM +0100, Jochem Kossen wrote: > > > This seems to be the only report that XFree86-4-clients is > > > broken. Can you please add this line under MAINTAINER in > > > x11/XFree86-4-clients/Makefile: > > > > Just for kicks, on IRC (OPN) i have met three people who had exactly the same > > problem...I'll advise them to just install XFree86-4-libraries manually > > first... > > It was later concluded that the problem isn't really how the port > is written but how ports handles updates by default. You need to > use a tool like portupgrade or remove all the XFree86* ports > before installing the new versions (=upgrading). And when you do > that your dependency chains in /var/db/pkg will be broken. The > only useful solution right now is portupgrade. > But...i WAS using portupgrade :-) (i did a portupgrade XFree86, and it chuckled on the XFree86-4-clients port) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020318205743.GA22186>