unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: tumashu <tumashu@163.com>
Cc: guix <guix-devel@gnu.org>
Subject: Re: A question about im-config
Date: Sun, 22 Jan 2017 02:15:26 +0100	[thread overview]
Message-ID: <20170122021526.1fb7e1d8@scratchpost.org> (raw)
In-Reply-To: <79e91191.7f7.159c3ade0c8.Coremail.tumashu@163.com>

Hi tumashu,

On Sun, 22 Jan 2017 08:57:49 +0800 (CST)
tumashu <tumashu@163.com> wrote:

> Im-config (https://anonscm.debian.org/cgit/collab-maint/im-config.git) is a shell script which
> used to manager input method by debian, I want to package it to guixsd, but many problem I faced:
> 
> 1.  How to deal with "/usr/bin/XXX" in schell script, for example: /usr/bin/fcitx, /usr/bin/ibux ....
> 2.  How to deal with "
> /usr/lib/*/qt5/plugins/platforminputcontexts/libfcitxplatforminputcontextplugin.
> "

Please substitute paths by store paths. The intention is to make sure that im-config always keeps doing the same thing every time it is invoked.

To do that you can add a phase by:

(arguments
 `(#:phases
   (modify-phases %standard-phases
     (add-after 'unpack 'patch-paths
       (lambda* (#:key inputs outputs #:allow-other-keys)
         (substitute* "im-config"
           (("/usr/bin/fcitx") (string-append (assoc-ref inputs "fcitx") "/bin/fcitx"))
...
))))))

  reply	other threads:[~2017-01-22  1:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-22  0:57 A question about im-config tumashu
2017-01-22  1:15 ` Danny Milosavljevic [this message]
2017-01-22  2:39   ` tumashu
2017-01-22  8:06     ` Integrating different input methods into Guix Danny Milosavljevic
2017-01-22 23:57       ` tumashu
2017-01-23  0:32         ` Integrating " Danny Milosavljevic
2017-01-23  6:38           ` tumashu
2017-01-26  8:02       ` Chris Marusich

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=20170122021526.1fb7e1d8@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    --cc=tumashu@163.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).