unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 3/3] gnu: Add CUPS service.
Date: Sun, 09 Oct 2016 16:37:13 +0200	[thread overview]
Message-ID: <87wphhfv1i.fsf@elephly.net> (raw)
In-Reply-To: <20161007202424.26732-3-wingo@igalia.com>


Andy Wingo <wingo@igalia.com> writes:

> * gnu/services/cups.scm: New file.
> * gnu/local.mk (GNU_SYSTEM_MODULES): Add gnu/services/cups.scm.
> * doc/guix.texi (Printing Services): New section.

[…]

> +The CUPS configuration controls the basic things about your CUPS
> +installation: what interfaces it listens on, what to do if a print job
> +fails, how much logging to do, and so on.  To actually add a printer,
> +you have to visit the @url{http://localhost:631} URL, or use a tool such
> +as GNOME's printer configuration services.  By default, configuring a
> +CUPS service will generate a self-signed certificate if needed, for
> +secure connections to the print server.
> +
> +One way you might want to customize CUPS is to enable or disable the web interface.  You can do that directly, like this:

This line is a little long.

> +Available @code{cups-configuration} fields are:
> +
> +@deftypevr {@code{cups-configuration} parameter} package cups
> +The CUPS package.
> +@end deftypevr
> +
> +@deftypevr {@code{cups-configuration} parameter} package-list extensions
> +Drivers and other extensions to the CUPS package.
> +@end deftypevr
> +
> +@deftypevr {@code{cups-configuration} parameter} files-configuration files-configuration
> +Configuration of where to write logs, what directories to use for print
> +spools, and related privileged configuration parameters.
> +
> +Available @code{files-configuration} fields are:
> +
> +@deftypevr {@code{files-configuration} parameter} log-location access-log
> +Defines the access log filename. Specifying a blank filename disables
> +access log generation. The value @code{stderr} causes log entries to be sent
> +to the standard error file when the scheduler is running in the foreground, or
> +to the system log daemon when run in the background. The value @code{syslog}
> +causes log entries to be sent to the system log daemon. The server name may be
> +included in filenames using the string @code{%s}, as in

Please use double-spacing between sentences.  (Also in paragraphs below
this one.)  Since this is generated documentation this should be fixed
in (gnu services cups).

> +@deftypevr {@code{cups-configuration} parameter} string default-paper-size
> +Specifies the default paper size for new print queues. "Auto" uses a
> +locale-specific default, while "None" specifies there is no default paper
> +size.  Specific size names are typically "Letter" or "A4".
> +Defaults to @samp{"Auto"}.
> +@end deftypevr

Should the possible values (“Auto”, “None”, “Letter”, “A4”) be wrapped
in @code or @samp?

At this point I have to take a break from looking at the documentation.
I had only a cursory look at gnu/services/cups.scm.

Wow.

~~ Ricardo

  parent reply	other threads:[~2016-10-09 14:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 20:24 [PATCH 1/3] gnu: cups-filters: Look for test page in own output dir Andy Wingo
2016-10-07 20:24 ` [PATCH 2/3] gnu: cups-filters: Use ghostscript with CUPS driver Andy Wingo
2016-10-09 14:17   ` Ricardo Wurmus
2016-10-10 12:50   ` Ludovic Courtès
2016-10-07 20:24 ` [PATCH 3/3] gnu: Add CUPS service Andy Wingo
2016-10-08  8:37   ` Andy Wingo
2016-10-09 13:02     ` Christopher Allan Webber
2016-10-09 14:37   ` Ricardo Wurmus [this message]
2016-10-10  8:32   ` Clément Lassieur
2016-10-10  8:55     ` Andy Wingo
2016-10-10 21:00       ` Ludovic Courtès
2016-10-09 14:14 ` [PATCH 1/3] gnu: cups-filters: Look for test page in own output dir Ricardo Wurmus
  -- strict thread matches above, loose matches on Subject: below --
2016-10-10 13:29 Andy Wingo
2016-10-10 13:30 ` [PATCH 3/3] gnu: Add CUPS service Andy Wingo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wphhfv1i.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=wingo@igalia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).