all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Faré <fahree@gmail.com>
To: 45725@debbugs.gnu.org
Subject: [bug#45725] Getting Gutenprint in Guix
Date: Fri, 13 Aug 2021 17:38:29 -0400	[thread overview]
Message-ID: <CAN7nBXdbUw2A3+K0TFDg+p4nd-iVp56RSjJYreqB+PGzU5O2gQ@mail.gmail.com> (raw)
In-Reply-To: <CAN7nBXfojBGbC0rYAhQ2EEtXW51g_wPNPfvsejy+cNjGaTJLjA@mail.gmail.com>

For the path issue, I'm not sure how you get CUPS to see the PPDs you
want, but once it does, the remaining issue should be to rewrite some
entries in the PPD to have a full path, most importantly the
cupsFilter entries, but in the PPD from macOS there were also other
entries with paths, that may or may not apply (except maybe the last
one?):
*APDialogExtension:
*APPrinterIconPath:
*APPrinterUtilityPath:
*APPrinterLowInkTool:
*APHelpBook:
*cupsICCProfile:

Note that the NixOS recipe creates a cups-progs derivation output that
has all the ppds and all the filter binaries (themselves symlinks to
the respective derivation outputs); then it symlinks that cups-progs
output to /var/lib/cups/path and configures to look for data and
binaries there, so it doesn't have to modify any PPD.




  reply	other threads:[~2021-08-13 21:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 11:38 [bug#45725] [PATCH] gnu: Add gutenprint John Doe
2021-01-08 11:51 ` [bug#45725] [PATCH v2] " John Doe
2021-01-08 12:50   ` Jonathan Brielmaier
2021-01-08 12:09 ` dftxbs3e
2021-01-09 11:12 ` [bug#45725] [PATCH v3] " John Doe
2021-01-19 14:56   ` [bug#45725] [PATCH] " Ludovic Courtès
2021-01-20  4:04     ` dftxbs3e
2021-08-13 20:03 ` [bug#45725] Getting Gutenprint in Guix Faré
2021-08-13 21:38   ` Faré [this message]
2021-08-14  3:34     ` Faré
2022-02-12  9:34 ` [bug#45725] [PATCH v4] gnu: Add gutenprint Brice Waegeneire
2022-04-30 11:21 ` [bug#45725] [PATCH] " Milan Svoboda
2022-04-30 15:09 ` Milan Svoboda

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

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

  git send-email \
    --in-reply-to=CAN7nBXdbUw2A3+K0TFDg+p4nd-iVp56RSjJYreqB+PGzU5O2gQ@mail.gmail.com \
    --to=fahree@gmail.com \
    --cc=45725@debbugs.gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.