* depends on foomatic-filters when a driver installs:
share/foomatic/db/source/.../*.ppd{,.gz}
* depends on foomatic-db-engine when a driver installs:
share/foomatic/db/source/.../*.xml
foomatic-db-engine now depends on foomatic-db (which itself depends on
nothing anymore).
This will ensure all the needed packages are installed for complete
foomatic-* use.
Some packages install both pre-created ppd and xml files, so theorically
it wouldn't need to depend on foomatic-db-engine, but we still do it
because we may want to regen the ppd file.
It's the best compromise I could come up with.
The important part for us is that "it is not required any more that for
Foomatic to return a PPD file for a given printer/driver combo that
there is an XML file for both the printer and the driver. One XML file
(either printer or driver) is enough when this file describes the
printer/driver relation."
That means that printers that did not appear before (i.e. one could not
create a custom ppd) where they were marked as supported will now
appear and work fine.
Add a link from foomatic-ppdfile to the CUPS driver directory so that
PPDs file will be created on demand (no need to hunt for them on
openprinting.org).
Merge MESSAGE from foomatic-db-gutenprint to be more coherent.
Rework dependencies:
foomatic-db{gutenprint,hpijs}->foomatic-db->foomatic-db-engine
Foomatic's database engine generates PPD files from the data in
Foomatic's XML database. It also contains scripts to directly generate
print queues and handle jobs.
work by and ok jakemsr@, ok kili@
