unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: swedebugia <swedebugia@riseup.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Idea: guix printer configuration generation
Date: Wed, 16 Jan 2019 16:00:30 +0100	[thread overview]
Message-ID: <CAE4v=pjTA+PmJ+UatZApd7s-SvbZk8NL80+DaJ3sGh9yGfucLg@mail.gmail.com> (raw)
In-Reply-To: <f5824903382ddd5dac85c14c54f8d44d@riseup.net>

Hello,

<swedebugia@riseup.net> ezt írta (időpont: 2019. jan. 16., Sze, 15:35):
>
> Hi
>
> I would rather not have to learn the CUPS web interface just to
> configure my printer. Do we have a way to do this yet from config.scm? I
> think we should abstract away everything CUPS.
>
> Maybe we could make a guix printer importer?
>
> The idea is to extract information about the printer via Guile and print
> what the user need to add to the config.scm.
>
> Something like this:
> $ guix printer
>
> "Found 1 USB printer: HP DeskJet 4330
> (cups-configuration
>  (printer
>    (name "HP DeskJet 4330"
>    (connection "usb://34234556"
>    (settings
>      (paper "a4"
>      (source "default"
>      ..."
>
> When the user adds this to their config.scm and reconfigures the printer
> JUST WORKS.
>
> Thoughts?
>
> --
> Cheers
> Swedebugia
>

I've found the CUPS config stuff somewhat problematic.
The config file is generated from another config file, and some other
things, that trigger
regenerating the config. Sometimes even the printer ink level is
regenerating cups configs,
which is really annoying. Modifying files in /etc is not a very nice
way to handle that indeed.
The problem is known upstream, and seems to be won't fix. If we could
get around that in any sane way,
I would be very happy.

Best regards,
g_bor

  reply	other threads:[~2019-01-16 15:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 14:35 Idea: guix printer configuration generation swedebugia
2019-01-16 15:00 ` Gábor Boskovits [this message]
2019-01-17  7:22   ` swedebugia
2019-01-17 12:08     ` Gábor Boskovits
2019-01-17 13:41       ` swedebugia

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='CAE4v=pjTA+PmJ+UatZApd7s-SvbZk8NL80+DaJ3sGh9yGfucLg@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=swedebugia@riseup.net \
    /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).