Comment 10 for bug 1081104

I looked into this yesterday. The 'osideploy' stage script tries
to jam the 'doctotext' executable into the service_user's 'bin'
directory. The process is fragile:

- It used to copy things into '~'; since Fabric does not run
  'sudo -i', the $HOME variable remained the real user's homedir,
  rather than the service_user's. I pushed a couple of commits
  fixing that today.

- It copies the 'doctotext' binary into '$service_user/bin' and
  adds that directory to 'PATH' in '$service_user/.bash_profile'.

- In addition to copying the 'doctotext' executable into the
  '$service_user/bin' directory, it copies some shared libs into
  '$service_user/lib', and then adds that directory to
  'LD_LIBRARY_PATH' in '$service_user/.bash_profile'.

The real breakage is this: Since '$service_user/.bash_profile'
only gets sourced during login (or the equivalent 'sudo -i'), it
won't be used when supervisor is started via Fabric.

I did some work yesterday trying to move 'doctotext' (version
0.13) into the bulidout. It's build is odd enough (no
'configure' script, weird builds of 3rd party stuff) that I gave
up after some hacking. I unpacked the 0.13 tarball, made it a
Git repository, and pushed it to the 'karlproject' Github
organization:

 https://github.com/karlproject/doctotext

While trying to get it to build, I reported some bugs against the
package on AMD64:

- "Linker failures due to missing '-fPIC'" (Ubuntu 12.04 x86_64),
  http://silvercoders.com/mantis/view.php?id=1230

- "Make failures due to unexpanded braces" (Ubuntu 12.04 x86_64),
  http://silvercoders.com/mantis/view.php?id=1231

I tried building it in my homedir on one of the gocept Gentoo
boxes, and ran into other weird errors.