Notices

leafpad has printing support. But I cannot select a printer.
I also packaged libgnomecups and libgnomeprint.
libgnomeprintui did not compile in scratchbox.

I can't add a printer without a cups server in any way that I can see. I don't have a cups server here right now, so I can't test anything. And I'm not talking about smb, no windows involvement at all. Just direct printing to a network attached postscript printer (via port 9100), which is very common these days. (Literally, you can cat filename.ps | telnet printer.ip.addr.here 9100 to print things.)

Just to be clear, at home I have a 192.168.* network, at work I have a 10.* network. You're saying I can configure an HP printer with a 10.* address while connected to the cups server on my 192.* home network, then later when I connect to my work network I would be able to print to the 10.* printer? If so, that's great, but if all the logic is there to print to a printer from the client, why do I need a server to configure that connection? If not, then I'm hosed without a cups server setup on every network I want to print on.

My understanding is that the cups client sends all it's work to the cups server, which then does the actual printing. If that's the case, then you can't reliably print on a network unless that network has a central cups server.

I did not test to configure multiple printers.
To install the cups-server I have to install
the inet superserver. If this doesn't make
problems on the phone, I will give it a try.
My fear is, that this could take much battery.

I have updated the cups packages and uploaded its dependencies.
Now all cups-packages, cups and cups-bsd included, should be
installable. However I did not test it on the device yet, so feedback
is welcome.

I seem to have some issue with ghostscript. Is there a specific repository I need to enable to get it? The one in devel appears to be broken in some way. I tried following it down the rabbit hole a bit by pulling the ghostscript deb from the repository and seeing where it breaks, but it started veering into the generic armel repositories and/or foreign debian repositories that I wasn't comfortable pulling from without knowing what I'm doing. cups-bsd pulled fine though.

after some hacking with dpkg, I got enough installed to get cupsd operational. ghostscript is still not operational (or installed), and libpam0 won't configure. But after fixing the broken dpkg listings (and manually linking a bit) I've gotten it up and running enough to add printers and printed a few test pages!

It's not pretty (and apt-get / dpkg still complain about busted packages) but it's working!

THANK YOU MASE!!!!!!!!!!! I've been waiting for this for ever!!!!

I did not have any dpkg problems in
scratchbox. However I did not test it
on the device. But it should be the same.
Anybody else having dpkg problems?

You were right! There were problems with ghostscript.
I fixed this. I also had to remove the ssl-cert dependency
from the server, because it was not possible for me to let
it configure correctly. But I uploaded ssl-cert. Maybe someone
can find the problem. It failes with the creation of ssl-cert-snakeoil.pem.

I could watch, that the internet connection is established very often.
I don't know, if it was before installing cups-client.

I also upoaded cups-pdf and bluez-cups.
I have no BT printer, so please test and report!