Re: [Gimp-print-devel] OSX support (Was Re: CITIZEN photo printers)

[<fo...@wa...>]

> On Feb 23, 2018, at 11:10 AM, Solomon Peachy <pi...@sh...> wrote:
> 
> On Fri, Feb 16, 2018 at 11:59:02AM -0500, fo...@wa... wrote:
>> There were some hiccups in getting all the binaries signed properly in
>> High Sierra but that has been accomplished. It’s rather straight
>> forward and I would be happy to make a write-up if you all want to
>> update the documentation on this. (Current documentation for OS X
>> packaging is not up to date).
> 
> I'm assuming you have to sign it with a propr Apple Developer key?
> 
> And I'm sure I speak for everyone here when I say that any documentation
> updates would be welcomed.  :)

I’ll do the write-up.

> 
>> The only stumble that I have found to making vendor specific OS X
>> variants is this: I have found NO way to have multiple variants of
>> gutenprint in /usr/libexec/cups/driver.  This is the part of the
>> system that populates the list of available “gutenprint printer
>> drivers” when you go to sys prefs and then hit the + button and then
>> calls the appropriate binary to make the ppd and install the printer.
>> The only way to distribute a Gutenprint-derived independant driver is
>> to pre-build the PPDs and place in
>>> Library>Printers>PPDs>Contents>Resources>. That’s the only sticking
>> point that I see to this.
> 
> Some of that is Gutenprint's fault; it's not intended to be
> parallel-installable across point releases, and I think the "driver"
> name is hardcoded to be 'gutenprint'.  It may be worth looking into
> allowing all executable names (and dependent data directories) to be
> changed at compile-time.  Perhaps a filename prefix not unlike how gcc
> cross compilers are set up?

If this is possible, I think it would be incredibly useful for a whole host of reasons.

> 
>> The other thing that I think is do-able (OS X specific) is the ability
>> to have ColorSync select an output ICC based on the Mediatype chosen.
>> That said, none of that programming has been done in genppd.c There is
>> only the generics (sRGB, etc) that have been defined for OS X.
> 
> Is this a generic feature that allows arbitrary options to be passed
> to ColorSync, or is it limited to a specific enumerated set?  I wonder
> if colord on Linux supports something similar.

I think it’s tide to Ink and Media setting key words. It’s a cups/ppd thing. https://www.cups.org/doc/spec-ppd.html#cupsICCProfile <https://www.cups.org/doc/spec-ppd.html#cupsICCProfile>
> 
> (Traditionally, one will set up multiple queues to the same backend
> device, one for each setting combination, and associate a unique ICC
> profile to each queue..)
> 
> - Solomon
> --
> Solomon Peachy			       pizza at shaftnet dot org
> Coconut Creek, FL                          ^^ (email/xmpp) ^^
> Quidquid latine dictum sit, altum videtur.
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
> Gimp-print-devel mailing list
> Gim...@li...
> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel