Saturday, June 18, 2011

A "new" CUPS is coming your way...

It's taken some time, but finally CUPS-1.4, a "new" major release of "the standards-based, open source printing system developed by Apple Inc. for Mac OS® X and other UNIX®-like operating systems", will be arriving for our stable users in the near future. The arch teams are testing, see bug 333781 for the details and progress.
So what does that mean? Well, technically there are a lot of new features since CUPS-1.3. In practice, I hope that some of the ancient Gentoo bugs like #341127 or #349496 go away now, since finally CUPS supports some of the features that modern desktop environments require. Also, right now CUPS is an embarrassing security hole, which will also be fixed by the upgrade.
In the version about to be stabilized, we do not support the new libusb-based interface for USB printers yet. Accessing USB printers will be done via the USB printer functionality in the kernel, as in CUPS-1.3. Why? Simply because there are still way too many problems with it. If you want to give it a try anyway, just keyword net-print/cups-1.4.6-r21 - the only difference between -r2 (the stable candidate) and -r21 is that -r21 supports the libusb backend with the usb use-flag. Cheers!

4 comments:

  1. Hi. Dabbott wrote in 2009 some tips to upgrading to cups-1.4 in Gentoo:
    http://gentoo-pr.org/node/30
    It's old, I wonder which items are still valid. Apparently
    > 1. disable kernel usblp:
    > CONFIG_USB_PRINTER=n
    does not apply now, right?

    Others are:
    > 2. delete /etc/cups
    > 3. (re-)install cups 1.4 with USE="usb"
    > 4. configure printer(s) from scratch
    > via the cups webinterface
    > 5. if your printer is a multifunction
    > device, be sure you got the udev rules
    > setting the device permissions in shape
    > so cups can access the device

    Thanks a lot for your effort in Gentoo.

    ReplyDelete
  2. For stable users:
    1. does not apply, we're using the old backend
    2. not needed
    3. see 1, not needed, not possible
    4. not needed
    5. err, well, maybe. dunno... :)

    Now if you want to use the ~arch ebuilds with libusb support, 1-4 probably also make sense. Not sure about 2.

    ReplyDelete
  3. Do you recommend using libusb instead of usblp in the kernel?

    ReplyDelete
  4. I dont have any experiences with libusb yet. I'll probably switch sometime in the future, to be able to figure out some of the open bugs, but so far I've been getting along fine with the old backend.

    ReplyDelete