I have some software I am about to ship (gradschool project) and I want to know on a unix machine what the best practices are for installing software.
I originally linked through
/usr/local/bin my project, but recently I looked into installing it by appending to the
.bashrc file for the specific user, with the special case that if the user is root, it appends to the global path rather than user specific.
This bought me some easy functionality additions as I can quickly link to other resources with a single variable addition to the
.bashrc folder of the installing user.
However, I am beginning to doubt this decision.
To append to path or not to append to path, that is the question. Whether 'tis nobler to symbolic link in
/usr/local/bin, or to take arms and append to an ever growing path variable.
It's a C++ back end with a TCL front end. There is also a java archive (created much earlier in my career) that the TCL front end launches. On top of this, there is a extension of the TCL front end that plays with another program with its own TCL interpreter. I need to provide the bwidget tcl package to the program with the interpreter. So providing the bwidget package and launching the jar file necessitates having a location to link to. Further more, I need to make it easy on the users as they are primarily chemistry users and are not very familure with unix and might be on mac.
The platform nees to work on Mac or Unix.
Ideally I want the user to be able to launch the TCL script with a single command and not make them remember the location.
This is a previously closed source project that is now open source and we want users to be able to easily compile and install the program
I am using make to create an install option.