From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 0/4] cn/jp/kr/tw fonts
Date: Mon, 22 Feb 2016 14:27:36 +0100 [thread overview]
Message-ID: <20160222132736.GA6329@jama> (raw)
In-Reply-To: <1455371527-11604-1-git-send-email-schnitzeltony@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 2293 bytes --]
On Sat, Feb 13, 2016 at 02:52:03PM +0100, Andreas Müller wrote:
> Did not yet find somebody reading them but to me they look authentic
All these get dependency on fontconfig making them TUNE_PKGARCH not
allarch.
I'll fix that in follow up commit, but keep that in mind when adding
more fonts.
> Andreas Müller (4):
> source-han-sans-cn-fonts: initial add 1.004
> source-han-sans-jp-fonts: initial add 1.004
> source-han-sans-kr-fonts: initial add 1.004
> source-han-sans-tw-fonts: initial add 1.004
>
> .../44-source-han-sans-cn.conf | 19 ++++++++++++
> .../ttf-fonts/source-han-sans-cn-fonts_1.004.bb | 34 ++++++++++++++++++++++
> .../44-source-han-sans-jp.conf | 19 ++++++++++++
> .../ttf-fonts/source-han-sans-jp-fonts_1.004.bb | 34 ++++++++++++++++++++++
> .../44-source-han-sans-kr.conf | 19 ++++++++++++
> .../ttf-fonts/source-han-sans-kr-fonts_1.004.bb | 34 ++++++++++++++++++++++
> .../44-source-han-sans-tw.conf | 19 ++++++++++++
> .../ttf-fonts/source-han-sans-tw-fonts_1.004.bb | 34 ++++++++++++++++++++++
> 8 files changed, 212 insertions(+)
> create mode 100644 meta-oe/recipes-graphics/ttf-fonts/source-han-sans-cn-fonts/44-source-han-sans-cn.conf
> create mode 100644 meta-oe/recipes-graphics/ttf-fonts/source-han-sans-cn-fonts_1.004.bb
> create mode 100644 meta-oe/recipes-graphics/ttf-fonts/source-han-sans-jp-fonts/44-source-han-sans-jp.conf
> create mode 100644 meta-oe/recipes-graphics/ttf-fonts/source-han-sans-jp-fonts_1.004.bb
> create mode 100644 meta-oe/recipes-graphics/ttf-fonts/source-han-sans-kr-fonts/44-source-han-sans-kr.conf
> create mode 100644 meta-oe/recipes-graphics/ttf-fonts/source-han-sans-kr-fonts_1.004.bb
> create mode 100644 meta-oe/recipes-graphics/ttf-fonts/source-han-sans-tw-fonts/44-source-han-sans-tw.conf
> create mode 100644 meta-oe/recipes-graphics/ttf-fonts/source-han-sans-tw-fonts_1.004.bb
>
> --
> 2.5.0
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-02-22 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 13:52 [PATCH 0/4] cn/jp/kr/tw fonts Andreas Müller
2016-02-13 13:52 ` [PATCH 1/4] source-han-sans-cn-fonts: initial add 1.004 Andreas Müller
2016-02-13 13:52 ` [PATCH 2/4] source-han-sans-jp-fonts: " Andreas Müller
2016-02-13 13:52 ` [PATCH 3/4] source-han-sans-kr-fonts: " Andreas Müller
2016-02-13 13:52 ` [PATCH 4/4] source-han-sans-tw-fonts: " Andreas Müller
2016-02-22 13:27 ` Martin Jansa [this message]
2016-02-22 13:30 ` [PATCH][meta-oe] source-han-sans-*-fonts: exclude fontconfig dependency with SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS Martin Jansa
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=20160222132736.GA6329@jama \
--to=martin.jansa@gmail.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