Date: Sat, 22 Aug 2015 14:55:09 -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.1508221448070.93055@wonkity.com> In-Reply-To: <20150823.025118.2214641030331335788.hrs@allbsd.org> References: <20150821.022521.792759762853683209.hrs@allbsd.org> <20150823.025118.2214641030331335788.hrs@allbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 23 Aug 2015, Hiroki Sato wrote: > Hiroki Sato <hrs@FreeBSD.org> wrote > in <20150821.022521.792759762853683209.hrs@allbsd.org>: > > hr> So I would suggest either of the following two plans: > hr> > hr> Plan A: Just remove print/ghostscript*-nox11. > ... > > hr> Plan B: Remove print/ghostscript*-nox11 and split the X11-dependent > hr> part of print/ghostscript9 into another port. > > Thank you all for your feedback! I committed changes for Plan B as > r395047. > > If you have a problem after this change, please report it to me. Thank you for working on this. It's not clear to me how people that currently have the old print/ghostscript should switch to the new version. 'portmaster -o print/ghostscript9-x11 ghostscript9-9.06_10' (in my case) or even just 'portmaster ghostscript9-9.06_10' turns into an endless loop: ===>>> print/ghostscript9-x11 >> print/ghostscript9-x11 >> ghostscript9-9.06_10 (2/2) ===>>> The print/ghostscript9 port moved to print/ghostscript9-x11 ===>>> Reason: Split into print/ghostscript9-base and print/ghostscript9-x11 That will continue to recurse, adding one more print/ghostscript9-x11 each time. UPDATING should show the correct method. Maybe just 'pkg delete -f ghostscript9-9.06_10' and then install print/ghostscript9-x11?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1508221448070.93055>