all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yoshinori Arai <kumagusu08@gmail.com>
To: swedebugia <swedebugia@riseup.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Where is gtk-update-icon-cache ... ?
Date: Sat, 2 Feb 2019 09:12:04 +0900	[thread overview]
Message-ID: <20190202001204.qge3m2bacpchx4ym@WaraToNora> (raw)
In-Reply-To: <4bfd8fa0-a40c-ca64-4194-99503f3bfa6e@riseup.net>

On Thu, Jan 31, 2019 at 03:58:40PM +0100, swedebugia wrote:
> On 2019-01-11 09:51, 荒井吉則 wrote:
> > On Fri, Jan 11, 2019 at 06:00:05AM +0100, Ricardo Wurmus wrote:
> >  > 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
> >  >
> > 
> > OK, I will do it.
> > However I think it is kind to ask will you install bin when someone
> > install like gtk+ or glibc with guix package -i <some library package>.
> 
> Your idea seems user friendly, but to implement it we would have to find a
> way to distinguish library-packages from other packages. I'm not sure how to
> programmatically distinguish if a package has a bin-output.
> 
> Right now you have to investigate the different outputs yourself e.g. by
> running:
> 
> $ guix package --show=gtk+
> 
> which lists the different outputs.
> 
> -- 
> Cheers Swedebugia

Hello,

I don't know is it not sure how to programmatically distinguish.
However, if library-packages would separete into library-only and bin
package, user can choose which one as debian dev package. I think.

      reply	other threads:[~2019-02-02  0:12 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
2019-01-11  8:51       ` 荒井吉則
2019-01-31 14:58         ` swedebugia
2019-02-02  0:12           ` Yoshinori Arai [this message]

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=20190202001204.qge3m2bacpchx4ym@WaraToNora \
    --to=kumagusu08@gmail.com \
    --cc=help-guix@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 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.