[OE-core] any subtle uses for hardcoded /etc instead of ${sysconfdir}?
Richard Purdie
richard.purdie at linuxfoundation.org
Sat Aug 2 10:13:41 UTC 2014
On Sat, 2014-08-02 at 04:13 -0400, Robert P. J. Day wrote:
> 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.
Not that I can think of offhand.
Cheers,
Richard
More information about the Openembedded-core
mailing list