From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/liberation
Date: Tue, 13 Jan 2009 11:28:21 +1100 [thread overview]
Message-ID: <20090113002821.GB32708@cloud.net.au> (raw)
In-Reply-To: <20090112124048.BBE95766E4@busybox.osuosl.org>
On Mon, Jan 12, 2009 at 12:40:48PM +0000, laird at uclibc.org wrote:
> -$(STAGING_DIR)/usr/share/fonts/.ttf: $(LIBERATION_DIR)/.unpacked
> +$(STAGING_DIR)/usr/share/fonts/LiberationMono-Bold.ttf: $(LIBERATION_DIR)/.unpacked
> -mkdir -p $(STAGING_DIR)/usr/share/fonts/liberation
> $(INSTALL) -m0644 $(LIBERATION_DIR)/*.ttf $(STAGING_DIR)/usr/share/fonts/liberation/
> touch -c $(STAGING_DIR)/usr/share/fonts/.ttf
>
> -$(TARGET_DIR)/usr/share/fonts/LiberationMono-Bold.ttf: $(STAGING_DIR)/usr/share/fonts/.ttf
> +$(TARGET_DIR)/usr/share/fonts/LiberationMono-Bold.ttf: $(STAGING_DIR)/usr/share/fonts/LiberationMono-Bold.ttf
> -mkdir -p $(TARGET_DIR)/usr/share/fonts/liberation
> $(INSTALL) -m0644 $(LIBERATION_DIR)/*.ttf $(TARGET_DIR)/usr/share/fonts/liberation/
> touch -c $(TARGET_DIR)/usr/share/fonts/.ttf
What's the purpose of the .ttf file touched in the staging and target
dirs?
Why is the font installed into the staging dir at all?
thanks
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2009-01-13 0:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 12:40 [Buildroot] svn commit: trunk/buildroot/package/liberation laird at uclibc.org
2009-01-12 13:05 ` Bernhard Reutner-Fischer
2009-01-12 14:19 ` Daniel James Laird
2009-01-13 0:28 ` Hamish Moffatt [this message]
2009-01-13 6:09 ` Peter Korsgaard
2009-01-13 7:30 ` danieljlaird at hotmail.com
-- strict thread matches above, loose matches on Subject: below --
2009-01-13 10:37 laird at uclibc.org
2009-01-15 21:52 ` Ulf Samuelsson
2009-01-15 23:15 ` Peter Korsgaard
2009-01-16 6:46 ` Ulf Samuelsson
2009-01-10 0:20 ulf at uclibc.org
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=20090113002821.GB32708@cloud.net.au \
--to=hamish@cloud.net.au \
--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