Removal of print/ghostscript*-nox11

Hiroki Sato hrs at
Sat Aug 22 21:50:51 UTC 2015

Warren Block <wblock at> wrote
  in <alpine.BSF.2.20.1508221448070.93055 at>:

wb> It's not clear to me how people that currently have the old
wb> print/ghostscript should switch to the new version.
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> ===>>> print/ghostscript9-x11 >> print/ghostscript9-x11 >>
wb> ghostscript9-9.06_10 (2/2)
wb> 	===>>> The print/ghostscript9 port moved to print/ghostscript9-x11
wb> 	===>>> Reason: Split into print/ghostscript9-base and
wb> 	print/ghostscript9-x11
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?

-- Hiroki
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <>

More information about the freebsd-ports mailing list