Date: Thu, 07 Jun 2007 18:53:49 -0400 From: Gerard <gerard@seibercom.net> To: User Questions <freebsd-questions@freebsd.org> Subject: Re: portupgrade -o oddness... Message-ID: <20070607184501.9F5E.GERARD-SEIBERT@seibercom.net> In-Reply-To: <20070607205905.GA45459@just.puresimplicity.net> References: <20070607205905.GA45459@just.puresimplicity.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday June 07, 2007 at 04:59:05 (PM) Josh Tolbert wrote: > Having successfully completed my update from Xorg 6.9 to Xorg 7.2, I decided > to install a few things, one of which required devel/bison2 instead of bison. > Usually, portupgrade -o would handle this for me, but lately it seems like > portupgrade -o doesn't want to replace ports. Has anyone else noticed this or > is there a known workaround/fix? > > (15:38:21 <hemi@demon:~>) $ pkg_info | grep bison > bison-1.75_2,1 A parser generator from FSF, (mostly) compatible with Yacc > (15:38:30 <hemi@demon:~>) $ sudo portupgrade -o devel/bison2 bison > (15:38:34 <hemi@demon:~>) $ sudo portupgrade -fo devel/bison2 bison > ---> Reinstalling 'bison-1.75_2,1' (devel/bison) > > The same problem occurred when I tried to replace ghostscript-gnu with > ghostscript-gpl as well. > > I'm using portupgrade-devel instead of portupgrade. Posting two identical questions except for the "Subject", eighteen minutes apart, to the same list does seem a bit tacky. Personally, I once tried to use the newer version of bison as opposed to the (I believe) bison-1.75, caused me grief. Since both versions cannot co-exist, at least not without quite a bit of user intervention, I found that I was getting broken dependencies, etc. being reported. I quickly reverted to the older version. I think, and as usually I am probably wrong, that only Open Office requires the newer version. It would be nice if there were a flag that would force the use of the newer version. It would be a welcome addition. Maybe something like: WITH-BISON2 that could be used on the command line or placed in the /etc/make.conf file for instance. -- Gerard
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070607184501.9F5E.GERARD-SEIBERT>