From: Mike Gerwitz <mtg@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Vagrant Cascadian <vagrant@debian.org>, 31366@debbugs.gnu.org
Subject: bug#31366: Missing icons in virt-manager user-interface
Date: Fri, 31 Aug 2018 21:12:11 -0400 [thread overview]
Message-ID: <87zhx29g2c.fsf@gnu.org> (raw)
In-Reply-To: <87ftyu1y0a.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 31 Aug 2018 15:11:49 +0200")
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
On Fri, Aug 31, 2018 at 15:11:49 +0200, Ricardo Wurmus wrote:
> Much like we pin search path recommendations to certain “root” packages
> we could do something similar for recommended packages. “glibc”, for
> example, could recommend “glibc-locales”; having a package installed
> that links with glibc (i.e. all of them) would result in a
> recommendation to also install the “glibc-locales” package. For “gtk+”
> the recommendation could be to also install one of the icon themes.
> Installing any package depending on “gtk+” would then lead to a
> recommendation to install one of these packages.
That seems like desirable behavior to me.
> Unfortunately, some of these recommendations will only be correct when
> using Guix on top of a foreign distribution, because we handle common
> scenarios on the Guix-based GNU system directly.
I can't comment on that, but in this virt-manager case, I did experience
the issue on GuixSD.
--
Mike Gerwitz
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
prev parent reply other threads:[~2018-09-01 1:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 0:10 bug#31366: Missing icons in virt-manager user-interface Vagrant Cascadian
2018-08-27 23:09 ` Vagrant Cascadian
2018-08-29 21:05 ` Vagrant Cascadian
2018-08-29 22:24 ` Leo Famulari
2018-08-30 1:01 ` Mike Gerwitz
2018-08-31 13:11 ` Ricardo Wurmus
2018-09-01 1:12 ` Mike Gerwitz [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
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=87zhx29g2c.fsf@gnu.org \
--to=mtg@gnu.org \
--cc=31366@debbugs.gnu.org \
--cc=rekado@elephly.net \
--cc=vagrant@debian.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 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).