Linked by Thom Holwerda on Wed 1st Aug 2007 10:24 UTC
BeOS & Derivatives Some interesting tidbits from the Haiku world. Firstly, the WebKit port bounty has reached its target, meaning Ryan Leavengood can get to work. Secondly, Vasper has made huge strides in getting CUPS ported to Haiku. And on a funny note, BeOS icons were used in the "24" TV show.
Thread beginning with comment 260039
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: cups
by vasper on Wed 1st Aug 2007 20:04 UTC in reply to "RE[4]: cups"
Member since:

I am just trying to port CUPS. It is not part of the Haiku tree and cannot be (correct me here if I am wrong) as it is GPL, not MIT. I guess it can be added to a Haiku base distro as an add-on.

I also don't know if I will even succeed. I want to see first how it goes. If I see I am close to a port I will see how I proceed.

As for foomatic, as I get it, is just an xml database with all drivers supported by CUPS and other spoolers. Also I would appreciate a suggestion, instead of a "I'm actually slightly dismayed" statement. What would you use by the way?

Edited 2007-08-01 20:06

Reply Parent Score: 3

RE[6]: cups
by Vanders on Wed 1st Aug 2007 20:56 in reply to "RE[5]: cups"
Vanders Member since:

The core of foomatic is the foomatic-rip script which is a honking big PERL script that sits in the critical print path and basically duplicates the functionality offered by the CUPS scheduler to drive Ghostscript and the printer drivers. It uses the foomatic XML database to provide information on how to do that. It was written back in the day when Open Source printing was an even bigger mess, and is capable of driving six (I think) different spoolers and various Postscript pipelines (Including enscript, any2ps and Ghostscript). Given that, foomatic is actually a pretty neat bit of work, but needless to say it makes it rather baroque.

What would you use by the way?

I'd do it the way I did it on Syllable and ditch Foomatic entirely. You can build most of the useful drivers such as Gutenprint and Splix as proper CUPS raster drivers, with their own CUPS PPDs that will allow the CUPS scheduler to drive the print pipeline itself. You lose the ability to use a handful of Ghostscript and non-standard drivers such as foo2zjs, but there is no PERL in the print pipeline and in my opinion, it's just a whole lot cleaner.

At worst, I was considering re-implementing a foomatic-alike in C that implements only the most basic functionality required to drive the pipeline (Which is basically knowing how to invoke Ghostscript or the non-standard filter) while leaving the rest of the scheduling up to CUPS. It's still messy, but it would eliminate PERL. I havn't decided if I'll do that yet though.

Reply Parent Score: 5

RE[7]: cups
by mikesum32 on Wed 1st Aug 2007 23:06 in reply to "RE[5]: cups"
mikesum32 Member since:

I think as long as CUPS is a separate program, you can distribute it, as long as it's isn't mixed with Haiku code.


The GNU LGPL applies to the CUPS and CUPS Imaging libraries located in the "cups" and "filter" subdirectories of the CUPS source distribution and in the "cups" include directory and library files in the binary distributions. The GNU GPL applies to the remainder of the CUPS distribution, including the "pdftops" filter which is based upon Xpdf.


The GNU LGPL relaxes the "link-to" restriction, allowing you to develop applications that use the CUPS and CUPS Imaging libraries under other licenses and/or conditions as appropriate for your application, driver, or filter.

Reply Parent Score: 2