Install tangle

Hal Murray hmurray at
Sat Jan 13 01:43:46 UTC 2018

Gary said.
> Yup.  Do we know if this can fail silently?

I tried it.  It's not silent.

Waf: Leaving directory `/home/murray/ntpsec/play/hgm/main'
Build failed
Traceback (most recent call last):
  File "/home/murray/ntpsec/play/.waf-1.9.14-d7f6128a2aa20a656027b134f0b4f4a6/
waflib/", line 145, in process
  File "/home/murray/ntpsec/play/.waf-1.9.14-d7f6128a2aa20a656027b134f0b4f4a6/
waflib/", line 556, in run
  File "/home/murray/ntpsec/play/.waf-1.9.14-d7f6128a2aa20a656027b134f0b4f4a6/
waflib/", line 145, in mkdir
    raise Errors.WafError('Could not create the directory %r'%self)
WafError: Could not create the directory /usr/local/lib/python2.7/site-package

>> What I really meant was won't work after installed.
> Well, that would be a hard question to answer.  Should we restart the ntpd
> daemon and see if it works?

ntpd doesn't depend on any of our libraries.  If it works before install, I 
expect it will keep working.  We could add a sanity check of running ntpd 
--version, both before and after the actual install.

We could similarly check ntpq post install.

> Wortse yet, in the case of installing into bounce directories, or cross
> compiling, how can you test  for 'it works". 

I'm willing to punt on cross compiles until we get a good example.

I don't know anything about bounce directories.  Does our install step have 
to know about them?  Should it work if we install them where we are told?

These are my opinions.  I hate spam.

More information about the devel mailing list