From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] hicolor-icon-theme: new package
Date: Tue, 7 Oct 2014 14:55:36 +0200 [thread overview]
Message-ID: <20141007125535.GC4028@rmm-p1267483> (raw)
In-Reply-To: <20141007142842.3c481ac5@free-electrons.com>
On Tue, Oct 07, 2014 at 02:28:42PM +0200, Thomas Petazzoni wrote:
> Dear Eric Le Bihan,
>
> On Tue, 7 Oct 2014 14:25:15 +0200, Eric Le Bihan wrote:
>
> > > I'm a bit confused by what this package does: it doesn't contain
> > > anything, and does not install anything except a huge number of
> > > directories (empty) in usr/share/icons/. Is this the intended behavior?
> > > I would have expected an icon theme to install some .svg or .png files,
> > > no?
> >
> > The hicolor icon theme is the *fallback* icon theme. As explained in the
> > specifications [1], this theme is required to have a place for third-party
> > applications to install their icons. If a icon is not found in the current
> > theme, then hicolor is the theme to look into.
> >
> > So the package just installs a directory structure as well as an index.
>
> Well, how can an empty thing be a fallback icon theme? That's kind of
> weird.
>
> Anyway, if you could update the help text to mention what it is
> exactly, it'd be great. Just to clarify to the user that it's normal
> for this package to not install anything except a bunch of empty
> directories.
Of course!
> > I added it to avoid some warnings when executing the gtk3-demo application.
>
> Sure, I certainly don't claim that it is unnecessary, I was just trying
> to understand what was going on.
>
> > When I'll provide a patch bumping libgtk3 to 3.14, I will also provide a
> > package for adwaita-icon-theme, which is a true icon theme, weighting 18 MB!
>
> Ouch. But all icons are present in multiple sizes, no? Are all sizes
> needed?
The adwaita-icon-theme package provides icons which sizes are 16x16, 24x24,
32x32, 48x48, 256x256 and of course some SVG ones. On the target its takes 20
MB of storage.
I'm no expert in icon loading, but it looks like if the requested size is not
found, then a smaller one is selected, upscaling is applied and you get
blurry icons.
Should I provide an option in the configuration menu to install only specific
sizes, or should removing the unwanted icons be left to the user (via
post-build script)?
Best regards,
ELB
next prev parent reply other threads:[~2014-10-07 12:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 16:21 [Buildroot] [PATCH 0/3] Re-introducing libgtk3 Eric Le Bihan
2014-09-23 16:21 ` [Buildroot] [PATCH 1/3] host-pkgconf: install pkg-config-native Eric Le Bihan
2014-10-06 19:47 ` Peter Korsgaard
2014-10-07 12:12 ` Eric Le Bihan
2014-09-23 16:21 ` [Buildroot] [PATCH 2/3] hicolor-icon-theme: new package Eric Le Bihan
2014-10-05 21:22 ` Thomas Petazzoni
2014-10-07 12:25 ` Eric Le Bihan
2014-10-07 12:28 ` Thomas Petazzoni
2014-10-07 12:50 ` Mike Zick
2014-10-07 12:55 ` Eric Le Bihan [this message]
2014-10-07 13:36 ` Thomas Petazzoni
2014-09-23 16:21 ` [Buildroot] [PATCH 3/3] libgtk3: " Eric Le Bihan
2014-09-23 16:23 ` Vicente Olivert Riera
2014-09-23 16:42 ` Gustavo Zacarias
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=20141007125535.GC4028@rmm-p1267483 \
--to=eric.le.bihan.dev@free.fr \
--cc=buildroot@busybox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox