The bluez-utils package now has a CUPS backend for bluetooth printers. How should it be shipped? The other CUPS backend which is shipped separate from CUPS itself is the one in samba-client. That one is just shipped in the samba-client RPM, and CUPS has a trigger script which makes a symlink to it from /usr/lib/cups/backend/ on installation of samba-client. Is there a reason why the trigger is done that way round -- in the _cups_ specfile rather than the samba one? Or why we can't ship the extra CUPS backend in a separate 'bluez-utils-cups' RPM which puts it directly into /usr/lib/cups/backend/ instead of making the symlink in a trigger script? Or any of the other possibilities? -- dwmw2
