all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: paren--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Luis Felipe" <luis.felipe.la@protonmail.com>, <58046@debbugs.gnu.org>
Subject: bug#58046: Poedit fails to open PO files
Date: Sat, 24 Sep 2022 20:25:56 +0100	[thread overview]
Message-ID: <CN4VMLVVFQWG.1QX02ALFLRU4I@guix-aspire> (raw)
In-Reply-To: <QpU9D0kpu_e0FL6Vtc2lBa14StqA4kE6533n1XBDNfY76GiIxAUt0wai_od13ucnRG_QVRUXw2JVRcrCzFYdruYqrGwmNfoGs5OVP0evVro=@protonmail.com>

On Sat Sep 24, 2022 at 8:02 PM BST, Luis Felipe via Bug reports for GNU Guix wrote:
> WORKAROUND
>
> Start Poedit in a guix shell that adds gettext:
>
> guix shell poedit gettext
> poedit
>
> Then, you can open the PO files normally.
>
> So it seems the package definition for Poedit is missing gettext as a run-time dependency (?).

What might be referred to as a "run-time dependency" is called a
"propagated input" in Guix, where a dependency of X is installed
whenever X itself is installed. They are generally considered
undesirable and should be avoided, so when we're faced with this
sort of problem we usually do:

  (inputs (list gettext))

and add a phase:

  (add-after 'unpack 'patch-invocations
    (lambda* (#:key inputs #:allow-other-keys)
      (substitute* "src/foo/bar.c"
        (("\"msgfmt\"")
         (string-append
          "\""
          (search-input-file inputs "bin/msgfmt")
          "\"")))))

    -- (




  reply	other threads:[~2022-09-24 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24 19:02 bug#58046: Poedit fails to open PO files Luis Felipe via Bug reports for GNU Guix
2022-09-24 19:25 ` paren--- via Bug reports for GNU Guix [this message]
2022-09-25 13:14   ` Luis Felipe via Bug reports for GNU Guix
2024-11-02 15:18 ` Luis Felipe via Bug reports for GNU Guix

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=CN4VMLVVFQWG.1QX02ALFLRU4I@guix-aspire \
    --to=bug-guix@gnu.org \
    --cc=58046@debbugs.gnu.org \
    --cc=luis.felipe.la@protonmail.com \
    --cc=paren@disroot.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.