Removal of print/ghostscript*-nox11

Stari Karp starikarp at yandex.com
Sat Aug 22 22:25:53 UTC 2015


On Sat, 2015-08-22 at 14:55 -0600, Warren Block wrote:
> On Sun, 23 Aug 2015, Hiroki Sato wrote:
> 
> > Hiroki Sato <hrs at FreeBSD.org> wrote
> >  in <20150821.022521.792759762853683209.hrs at 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?
> _______________________________________________
I did pkg delete and than install again and everything works as before.




More information about the freebsd-ports mailing list