Created attachment 146284 [details]
% make -C /usr/ports/graphics/ImageMagick-nox11 all-depends-list | grep ghost
graphics/ImageMagick-nox11 now depends on print/ghostscript9 but this is not user friendly because when people want to install ImageMagick-nox11, they don't want to install X11 relevant ports.
According to Mk/bsd.port.mk around line 1954, ghostscript with -nox11 suffix will be installed if WITHOUT_X11 variable is defined. I think WITHOUT_X11 should be defined when X11 option is disabled.
will ghostcript 9 conflict with ghostscript-nox11?
Maybe it is this way to pick the most common of the two conflicting packages (if they conflict).
That said, if they are picking -nox11 packages, then likely they use -nox11 versions everywhere.
over to maintainer
This time, over to maintainer.
Yes, ghostscript9 conflicts with ghostscript9-nox11. When I try to upgrade ImageMagick-nox11, portmaster installs ghostscript9 even though ghostscript9-nox11 is already installed.
% pkg version -Ivl\<
ImageMagick-nox11-126.96.36.199_1,1 < needs updating (index has 188.8.131.52_2,1)
% pkg info |grep ghostscript
ghostscript9-nox11-9.06_7 Ghostscript 9.x PostScript interpreter
% sudo portmaster ImageMagick-nox11
===>>> The following actions will be taken if you choose to proceed:
Upgrade ImageMagick-nox11-184.108.40.206_1,1 to ImageMagick-nox11-220.127.116.11_2,1
===> Installing for ghostscript9-9.06_7
===> Checking if ghostscript9 already installed
===> Registering installation for ghostscript9-9.06_7 as automatic
pkg-static: ghostscript9-9.06_7 conflicts with ghostscript9-nox11-9.06_7 (installs files into the same place). Problematic file: /usr/local/bin/dvipdf
Note: in order to use the script "dvipdf", dvips must be installed.
This program may be provided by either print/dvips or print/dvipsk-tetex
(print/dvipsk-tetex may be preferable since it doesn't conflict with
FAPIfontmap and FAPIcidfmap in /usr/local/share/ghostscript/9.06/Resource/Init
have to be configured if you want to use FAPI feature.
*** Error code 70
This is actualy a bug in bsd.port.mk. The logic that switches between the normal ghostscript port and -nox11 doesn't check OPTIONS for X11.
This is tricky to do because not all ports might set the X11 option.
When I install -nox11 suffix port, all depends ports if have -nox11
Mistake posting a comment. Anyway, generalized the problem.
-nox11 ports should depends on -nox11 ports if depended ports have -nox11 option.
Could we have a non-general patch to fix just the imagemagick vs ghostscript situation.
It's understood that this is a more generic problem but as far as I can see, it breaks all those nice poudriere builds since since half a year?
pkg's default packages are useless for running on servers, since they're all desktop-x11-y.
self building doesn't work since ports are too broken.
What I'm trying to say:
This isn't a good starting situation to let it dangle and wait till we can come up with a nice and clean generic solution.
I'm also interested in a solution for this as I have the same issue as the original poster.
I think that importance should be changed because it affects all people that uses FreeBSD for servers (Which is probably most of the people that use FreeBSD).