Joerg Sonnenberger writes:

> On Thu, Oct 11, 2007 at 11:45:07AM +0000, David Sainty wrote:
> > I solve this case here by explicitly disabling CUPS support.  For
> > normal cases this should mean "No change", but in exotic cases it fixes
> > the build and install.
> 
> Does the CUPS support add other dependencies or just build the
> pstoraster binary? If it is the latter, I would strongly prefer to make
> that the default and be able to just drop the special handling for CUPS.

It would add a dependency on "cups".  Elsewhere, "cups" is often a
package option, so it might be a shame to pull it in here.  Making
"cups" a package option on "print/ghostscript" is easy of course, and
is one solution.

But there is another alternative that is possibly more correct, but
much more work.  It may makes more sense to have a
"print/ghostscript-cups" that depends on "print/cups-lib", and have
"print/cups" depend on both (possibly with a "ghostscript" package
option for "print/ghostscript-cups", but likely by default it would be
enabled).

The idea being that if you want "print/cups", getting
"print/ghostscript-cups" by default is probably a good thing.  But you
can't do that as it stands without getting a dependency loop.

But I also didn't look deeply into this, since I had another solution
that maintained the status quo.

Cheers,

Dave