Emulate texlinks, so that those pesky symlinks are now in the packing list.
Minor plist tidy-ups that help fix the upgrade (see recent quirks commit).
OK kili@, espie@
Relatorio is a templating library which provides a way to easily output
several kinds of files (odt, ods, png, svg, ...). Support for more
filetypes can be easily added by creating plugins for them.
Relatorio also provides a report repository allowing you to link python
objects and report together, find reports by mimetype/name/python
This is a required dependency for the tryton framework which I'm working
on porting.
ok jasper@
PDF-Shuffler is a small python-gtk application, which helps the user to
merge or split pdf documents and rotate, crop and rearrange their pages
using an interactive and intuitive graphical interface. It is a frontend
for python-pyPdf.
ok ajacoutot@
cups-pk-helper is a PolicyKit helper to configure cups with fine-grained
privileges.
For example, it's possible to let users enable/disable printers without
requiring a password, while still requiring a password for editing
printer settings.
ok jasper@
Python bindings for the Poppler PDF rendering library, needed by an
upcoming pdfshuffler port.
With tweaks and ok jasper@
Grumblings about poppler api changes from kili@
PLIST and delete everything under the @sample'd directory instead of the
directory itself to prevent a warning from pkg_delete(1) trying to
remove a non existing directory and to help preventing left-over files
and directories.
foomatic-rip will be able to find the filters installed there
(e.g. foomatic-rip-hplip) when it is not started from cups but for e.g.
lpd(8).
tested by oga@, thanks!
* 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.
