Date: Sat, 22 Aug 2015 19:08:53 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Hiroki Sato <hrs@FreeBSD.org> Cc: ports@FreeBSD.org Subject: Re: Removal of print/ghostscript*-nox11 Message-ID: <alpine.BSF.2.20.1508221858250.93055@wonkity.com> In-Reply-To: <20150823.064920.51565180111392661.hrs@allbsd.org> References: <20150821.022521.792759762853683209.hrs@allbsd.org> <20150823.025118.2214641030331335788.hrs@allbsd.org> <alpine.BSF.2.20.1508221448070.93055@wonkity.com> <20150823.064920.51565180111392661.hrs@allbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 23 Aug 2015, Hiroki Sato wrote: > Warren Block <wblock@wonkity.com> wrote > in <alpine.BSF.2.20.1508221448070.93055@wonkity.com>: > > wb> It's not clear to me how people that currently have the old > wb> print/ghostscript should switch to the new version. > wb> > wb> 'portmaster -o print/ghostscript9-x11 ghostscript9-9.06_10' (in my > wb> case) or even just 'portmaster ghostscript9-9.06_10' turns into an > wb> endless loop: > wb> > wb> ===>>> print/ghostscript9-x11 >> print/ghostscript9-x11 >> > wb> ghostscript9-9.06_10 (2/2) > wb> > wb> ===>>> The print/ghostscript9 port moved to print/ghostscript9-x11 > wb> ===>>> Reason: Split into print/ghostscript9-base and > wb> print/ghostscript9-x11 > wb> > wb> That will continue to recurse, adding one more print/ghostscript9-x11 > wb> each time. UPDATING should show the correct method. Maybe just > wb> 'pkg delete -f ghostscript9-9.06_10' and then install > wb> print/ghostscript9-x11? > > Does r395051 fix this issue? 'portmaster ghostscript' did correctly replace the old ghostscript with ghostscript-base, but ghostscript-x11 was not installed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1508221858250.93055>