<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Ok. Then it simplifies the job and everything is getting more straightforward.</div><div><br></div><div>Another question. What about creating default.key file that is authorized for everything. Is it also should be deferred to the package manager?</div><div><br></div><div>---</div><div>Alex</div><br><div><div>On Mar 12, 2014, at 11:42 AM, Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu">shijunxiao@email.arizona.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p dir="ltr">"./waf install" or "make install" is a command to *install* a software. It just needs to install a **sample** configuration file to /etc/ndn/nfd.conf.sample .<br>
`nfd` program requires a command line argument for the path to configuration file. User must copy the sample cconfiguration file, and pass its path as the argument.</p><p dir="ltr">Package has a post-install step, which should:</p><p dir="ltr">1. copy the sample to /etc/ndn/nfd.conf , if it doesn’t exist<br>
2. perform a dry-run, to guard against an incompatible configuration<br>
3. setup upstart job that has the configuration file path</p><p dir="ltr">Yours, Junxiao</p>
</blockquote></div><br></body></html>