The affected ports are the ones with gettext as a run-dependency
according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT
in Makefile (29 of them).
PR: ports/124340
Submitted by: edwin@
Approved by: portmgr (pav)
with the current version of CUPS. Also, many improvements. Fix a bit in the
plist. Bump thePORTREVISION.
libgnomecups:
--------------------
* patch-20_parse-dot-cups-lpoptions: Parse ~/.cups/lpoptions.
* patch-21_fix-islocal: Check whether the printer URI starts with http://,
ipp://, or smb:// to test whether its local or not.
* patch-22_ignore-ipp-not-found: Do not warn on stderr in case of
IPP_NOT_FOUND.
* patch-23_replace-set-printer-attrs: Replace IPP_SET_PRINTER_ATTRIBUTES with
CUPS_ADD_MODIFY_PRINTER.
* patch-24_mem-leak: Fix memory leak in
gnome_cups_request_add_requested_attributes().
* patch-25_browsed_ppds: Fix PPD retrieval for printers picked up with cups
browsing.
--------------------
gnome-cups-manager:
--------------------
* patch-24_printer_properties_name_entry: Doesn't allow changing of printer
names, but the GUI pretends to.
* patch-25_properties_on_add: Don't open up a printer properties on a fresh
add of a printer. CUPS isn't synced yet, so it causes problems.
* patch-26_remove-no-cups-dialog: Don't show a dialog when CUPS isn't found.
* patch-27_dont-request-additional-attributes: Avoid calling
gnome_cups_request_add_requested_attributes() since CUPS returns all
attributes by defaults anyway.
* patch-change_uri_fix: Fix the URI change.
* patch-gutenprint_driver_name: Do not crash if a PPD file name does not
contain a '/'.
* patch-password_field_garbage: When editing SMB connection attributes, do not
set the password input field to the value of 'resource' (which is 'smb'). We
do not get the password in cleartext, so just leave the field blank.
* patch-select_eintr_crash: Do not bail out if select() fails with EINTR,
which is a valid case.
* patch-ui_edit_name_description: Add gnome-cups-add step to change printer
name, description, and location.
* patch-ui_startbox: Improvement on startup, run progress bar in the first
startup to scan the printer database.
* patch-ui_tooltip: Adjust tooltip for cups network printer installation.
--------------------
PR: ports/106972
Reported by: Werner <elvis69@arcor.de>
Tested by: Werner <elvis69@arcor.de>
in bsd.autotools.mk essentially makes this a no-op given that all the
old variables set a USE_AUTOTOOLS_COMPAT variable, which is parsed in
exactly the same way as USE_AUTOTOOLS itself.
Moreover, USE_AUTOTOOLS has already been extensively tested by the GNOME
team -- all GNOME 2.12.x ports use it.
Preliminary documentation can be found at:
http://people.FreeBSD.org/~ade/autotools.txt
which is in the process of being SGMLized before introduction into the
Porters Handbook.
Light blue touch-paper. Run.
the libtoolX ports instead of the one included with each port. Ports that
set USE_LIBTOOL_VER=X will now use the ports version of libtool instead of
the included version. To restore previous behavior, use the new macro,
USE_INC_LIBTOOL_VER. Both macros accept the same argument: a libtool version.
For example, to use the ports version of libtool-1.5, add the following to
your Makefile:
USE_LIBTOOL_VER= 15
To use the included version of libtool with extra hacks provided by
libtool-1.5, add the following to your Makefile:
USE_INC_LIBTOOL_VER= 15
With this change, ports that had to add additional libtool hacks to prevent
.la files from being installed or to fix certain threading issues can now
delete those hacks (after appropriate testing, of course).
PR: 63944
Based on work by:eik and marcus
Approved by: ade (autotools maintainer)
Tested by: kris on pointyhat
Bound to be hidden problems: You bet
Begin autotools sanitization sequence by requiring ports to explicitly
specify which version of {libtool,autoconf,automake} they need, erasing
the concept of a "system default".
For ports-in-waiting:
USE_LIBTOOL=YES -> USE_LIBTOOL_VER=13
USE_AUTOCONF=YES -> USE_AUTOCONF_VER=213
USE_AUTOMAKE=YES -> USE_AUTOMAKE_VER=14
Ports attempting to use the old style system after June 1st 2004 will be
sorely disappointed.
