* any subtle uses for hardcoded /etc instead of ${sysconfdir}?
@ 2014-08-02 8:13 Robert P. J. Day
2014-08-02 10:13 ` Richard Purdie
0 siblings, 1 reply; 2+ messages in thread
From: Robert P. J. Day @ 2014-08-02 8:13 UTC (permalink / raw)
To: OE Core mailing list
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
========================================================================
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: any subtle uses for hardcoded /etc instead of ${sysconfdir}?
2014-08-02 8:13 any subtle uses for hardcoded /etc instead of ${sysconfdir}? Robert P. J. Day
@ 2014-08-02 10:13 ` Richard Purdie
0 siblings, 0 replies; 2+ messages in thread
From: Richard Purdie @ 2014-08-02 10:13 UTC (permalink / raw)
To: Robert P. J. Day; +Cc: OE Core mailing list
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-08-02 10:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-08-02 8:13 any subtle uses for hardcoded /etc instead of ${sysconfdir}? Robert P. J. Day
2014-08-02 10:13 ` Richard Purdie
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.