unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: 荒井吉則 <kumagusu08@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Where is gtk-update-icon-cache ... ?
Date: Fri, 11 Jan 2019 06:00:05 +0100	[thread overview]
Message-ID: <87d0p34wmi.fsf@elephly.net> (raw)
In-Reply-To: <CAH2wgjgo7z6x3WnYCsgj=6evcmAL_s+mgvAjTc3LZP4QbWX6DQ@mail.gmail.com>

Hi,

荒井吉則 <kumagusu08@gmail.com> writes:

> I found /gnu/store/...-gtk+-3.24.0-bin/bin/gtk-update-icon-cache. Also
> found /gnu/store/...-glibc-2.28/bin/locale.
>
> Why not these command make symlink to ~/.guix-profile/bin ?

There will be a lot of files in /gnu/store that are not linked to any
profile.  That’s on purpose.

If you want to install gtk-update-icon-cache you need to install the
“gtk+:bin” package to a profile, e.g. by doing

    guix package -i gtk+:bin

> And  I did gtk-update-icon-cache -t -f --include-image-data
> ~/.guix-profile/share/icons/hicolor.
> It return permission error that is directory read only.

This is also by design.  ~/.guix-profile is read-only because it lives
in /gnu/store (via a series of symlinks).  Nothing in /gnu/store can be
changed; you can only add to it by using the “guix” commands.

The is usually no need to run gtk-update-icon-cache manually as it is
run in a profile hook when building a new generation of a profile.

-- 
Ricardo

  reply	other threads:[~2019-01-11  5:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10  1:23 Where is gtk-update-icon-cache ... ? 荒井吉則
2019-01-11  0:00 ` Leo Famulari
2019-01-11  4:01   ` 荒井吉則
2019-01-11  5:00     ` Ricardo Wurmus [this message]
2019-01-11  8:51       ` 荒井吉則
2019-01-31 14:58         ` swedebugia
2019-02-02  0:12           ` Yoshinori Arai

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=87d0p34wmi.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=kumagusu08@gmail.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.
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).