From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 1/5] fontforge: update to 20150824
Date: Fri, 28 Aug 2015 13:57:24 +0300 [thread overview]
Message-ID: <55E03E94.50705@linux.intel.com> (raw)
In-Reply-To: <1858940.qR1UtCzzK3@peggleto-mobl.ger.corp.intel.com>
On 08/27/2015 06:28 PM, Paul Eggleton wrote:
> A different person asking doesn't make the idea any more palatable (not to me,
> at least...)
>
> Since this wasn't explored earlier though, if we absolutely must upgrade
> liberation-fonts and there really is no alternative to distributing this font
> other than to build it from source then we're left with little choice, but are
> both of those things true?
I haven't explored the situation in detail; I've only seen the
RECIPE_NO_UPDATE_REASON that someone else added, and took what it says
at face value: it is desirable to update the fonts, but absence of
fontforge in oe-core prevents it.
Alex
next prev parent reply other threads:[~2015-08-28 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 14:53 [PATCH 0/5] updates and fixes again Andreas Müller
2015-08-27 14:53 ` [PATCH 1/5] fontforge: update to 20150824 Andreas Müller
2015-08-27 14:59 ` Alexander Kanavin
2015-08-27 15:10 ` Andreas Müller
2015-08-27 15:28 ` Paul Eggleton
2015-08-28 10:57 ` Alexander Kanavin [this message]
2015-08-27 14:53 ` [PATCH 2/5] xfce4-icon-theme: remove Andreas Müller
2015-08-27 14:53 ` [PATCH 3/5] rodent-icon-theme: add RPROVIDES/RREPLACE/RCONFLICTS for xfce4-icon-theme Andreas Müller
2015-08-27 14:53 ` [PATCH 4/5] xfce4-notifyd: fix build for libnotify 0.7.x Andreas Müller
2015-08-27 14:53 ` [PATCH 5/5] gnome-disk-utility: " Andreas Müller
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=55E03E94.50705@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--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