Re: [Gimp-print-devel] CUPS backend -- move to its own directory?

[Solomon P. <pi...@sh...>]

On Fri, May 24, 2019 at 07:26:13PM -0400, Robert Krawitz wrote:
> That's a lot better.  Can your test use the rotor setup (see the CUPS
> and run-testpattern-2 tests to see how that works), so jobs can be
> farmed off to different machines?  Currently it's split 5 ways.

The tests implement a similar mechanism but the script does its own 
forking.  I'll see about pulling that out so a specific rotor number can 
be invoked arbitrarily..

> Would it be useful to have an option emit printer data streams, or are
> those simply the unprocessed data from the driver with some out of
> band protocol that can't be captured as a data stream?  That would
> allow saving checksums from these tests like we do from the
> run-testpattern-2 tests.

I don't think so; most of the time the data going out is substantially 
similar to what goes in, but the backend has to do a bunch of 
interactive stuff to make sure it's okay to send the raster data and 
handle errors that inevitably pop up.

That said, emulating the printer would be substantially usful, but it's 
really hard to justify that level of effort.  :)

 - Solomon
-- 
Solomon Peachy			       pizza at shaftnet dot org
Coconut Creek, FL                          ^^ (email/xmpp) ^^
Quidquid latine dictum sit, altum videtur.