Open truedat101 opened 9 years ago
The ccnx-post-install script in its current form seems to not do much of anything. Reducing the number off steps to get started is a big idea that should be taken seriously.
The Tutorial expects everything under a hardcoded /usr path, so at this point, the configure script for the tutorial (not part of the binary) needs to also just look for some CCN_HOME dir.
Referencing instructions in the README: http://www.ccnx.org/releases/README-r20150316.txt
It is undesirable to drop software into /usr or any root protected areas of the OS without a means to easily and cleanly upgrade or remove the software. It would be preferred to offer an installer script that also includes an uninstaller, or better, a package for the target OS (deb, rpm, brew, arch).
It also isn't clear the motivation for requiring the CCN software to be located in the usr or usr/local dirs. Environment variables can resolve general issues of loading libraries (CCNX_HOME), and binaries should go into the path anyway.
It may be the case the thought is that normal researchers will be ok to install into a VM, and therefore won't care about these issues mentioned. To grow the audience it is needed truly make the software accessible beyond researchers.