Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] gtk+ and fonts
Date: Mon, 07 Dec 2009 16:42:02 +0000	[thread overview]
Message-ID: <1260204122.779.75.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <4B1D222A.90105@kernelconcepts.de>

On Mon, 2009-12-07 at 16:41 +0100, Florian Boor wrote:
> our current GTK+ packages recommend a single Truetype font (ttf-dejavu-sans).
> This might pull in a quite large font collection that might be different from
> what the user wants. For a Japanese image e.g. you might not want these at all
> or you might just want different fonts (like the Android ones).
> 
> I would be fine removing this RRECOMMENDS entry without any replacement. Another
> option would be to create a virtual provider for basic ttf fonts and define a
> matching run time dependency.

Just removing that RRECOMMENDS (or weakening it to RSUGGESTS) would run
the risk of breaking images that are currently depending on it.  I
suspect there are probably quite a few of those and this might not be a
good idea.

Creating some kind of virtual for gtk+ to depend on instead of a
particular concrete font does sound like the best way forwards with
this.  And, of course, individual DISTROs are welcome to eliminate that
RRECOMMENDS in the gtk+ packaging.

p.





  parent reply	other threads:[~2009-12-07 16:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07 15:41 [RFC] gtk+ and fonts Florian Boor
2009-12-07 16:33 ` Koen Kooi
2009-12-07 16:42 ` Phil Blundell [this message]
2009-12-07 17:05   ` Florian Boor

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=1260204122.779.75.camel@mill.internal.reciva.com \
    --to=philb@gnu.org \
    --cc=openembedded-devel@lists.openembedded.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox