Date: Wed, 14 Nov 2007 16:52:27 GMT From: Joseph S Atkinson <jsatkinson@embarqmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: standards/118047: SUGGESTION: /etc/printcap vs mergemaster Message-ID: <200711141652.lAEGqRNt090527@www.freebsd.org> Resent-Message-ID: <200711141700.lAEH02Q9059170@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 118047 >Category: standards >Synopsis: SUGGESTION: /etc/printcap vs mergemaster >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-standards >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Nov 14 17:00:02 UTC 2007 >Closed-Date: >Last-Modified: >Originator: Joseph S Atkinson >Release: 7.0-BETA2 >Organization: >Environment: >Description: The default file /etc/printcap is an example file that does not provide any working functionality to the process it configures (lpr) in it's default state. A working configuration must be either manually set up or is automatically generated by ports, such as CUPS, to function. When invoking mergemaster, it will detect changes to /etc/printcap and ask for user input. This seems to be rather fruitless since any changes made to the file are (theoretically) intended, or will be overwritten automatically by a ports based print spooler on next daemon restart. I am suggesting that the example /etc/printcap be moved into /usr/share/examples/printing/printcap where it would seem more at home and be less likely to cause confusion and/or collision with local configurations. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200711141652.lAEGqRNt090527>