From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: any subtle uses for hardcoded /etc instead of ${sysconfdir}?
Date: Sat, 2 Aug 2014 04:13:32 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1408020410230.13352@localhost> (raw)
occasionally, i run across stuff like this (here, under
recipes-support):
$ grep -r "/etc" nss*
nss/files/nss-CVE-2013-1740.patch:+ *
(SSL_ForceHandshake/PR_Recv/PR_Send/etc.) needed to finish the handshake.
nss/nss.inc: mkdir -p ${D}/etc/pki/nssdb/
nss/nss.inc: certutil -N -d ${D}/etc/pki/nssdb/ -f ./empty_password
nss/nss.inc: chmod 644 ${D}/etc/pki/nssdb/*.db
nss-myhostname/nss-myhostname_0.3.bb: -i $D/etc/nsswitch.conf
nss-myhostname/nss-myhostname_0.3.bb: -i $D/etc/nsswitch.conf
$
is there any reason for hard-coding "/etc" into those filenames,
rather than "${sysconfdir}"? i can submit a quick patch to tweak that,
but i always wonder if there's something subtle going on underneath
that i'm unaware of.
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-08-02 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 8:13 Robert P. J. Day [this message]
2014-08-02 10:13 ` any subtle uses for hardcoded /etc instead of ${sysconfdir}? Richard Purdie
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.1408020410230.13352@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.