From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
<openembedded-devel@lists.openembedded.org>
Subject: avoiding hard-coded filenames in package file lists
Date: Mon, 14 Jul 2014 19:35:39 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407141932020.6827@localhost> (raw)
occasionally, i still trip across stuff like this (this is from
oe-core):
meta/recipes-graphics/ttf-fonts/ttf-bitstream-vera_1.10.bb:FILES_${PN} = "/etc ${datadir}/fonts"
i'm assuming that one should avoid hard-coding names like "/etc" in
this case, and instead use (in this case) ${sysconfdir}, yes?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2014-07-14 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 23:35 Robert P. J. Day [this message]
2014-07-15 7:11 ` avoiding hard-coded filenames in package file lists Henning Heinold
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=alpine.LFD.2.11.1407141932020.6827@localhost \
--to=rpjday@crashcourse.ca \
--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