This should be the last part of the renaming operation for print/cups to
print/cups-base.
Rationale: packages depending on CUPS but not relying on a functional
printing setup only need to depend on print/cups-base (equivalent to the
former print/cups). The new print/cups now depends on print/cups-base
and on print/cups-filters, thus directly providing a functional printing
setup. This bump reflects this change of dependency.
As discussed on tech-pkg@
This is with the notable exception of meta-pkgs/desktop-gnome, which I
believe implies a fully functional cups.
This is still missing revision bumps - I'll be right there (first time I
am doing this on so many packages at a time).
As discussed on tech-pkg@
Based on patches from Edgar Fuß.
0.64 Thu Jun 08 20:10:00 2017
- Report the printer-state attribute and support non-string device
attributes in general by Edgar Fuß
0.63 Thu Oct 31 09:15:00 2016
- Fix segfaults in Net::CUPS::PPD::getNextOption when enumerating
options by Alexis Bienvenüe
- Fix bad free() when finalizing the result of getDestinations()
by Alexis Bienvenüe
- Fix a spelling mistake by Gregor Herrmann
- Update support information
0.62 Thu Jul 21 08:20:30 2016
- Fix version check on CUPS 2 by Mathieu Simon
- Fix compatibility with CUPS >= 1.6 by contyk
Problems found locating distfiles:
Package acroread7: missing distfile AdobeReader_enu-7.0.9-1.i386.tar.gz
Package acroread8: missing distfile AdobeReader_enu-8.1.7-1.sparc.tar.gz
Package cups-filters: missing distfile cups-filters-1.1.0.tar.xz
Package dvidvi: missing distfile dvidvi-1.0.tar.gz
Package lgrind: missing distfile lgrind.tar.bz2
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
