Re: Packaging proprietary software
2012/1/18 Ivan Reche <email@example.com>
Thanks for the tips. It seems like a nice solution.
Can someone recommend me a Debian's binary package for use as an example to create mine?
2012/1/16 Ansgar Burchardt <firstname.lastname@example.org>
For site packages, I would install the program to /opt/whatever as it wants and install a wrapper script in /usr/bin that sets the required environment variables and starts the program. This way users have the program in their $PATH by default and the environment stays clean.
On 01/16/2012 03:27 PM, Ivan Reche wrote:
The package is just a directory with lots of binaries and it likes to
install itself in /opt. Besides that, it needs to set some environment
variables (similar to JAVA_HOME and friends).
What is the best way to approach this? Do I change the PATH environment
variable to point to, lets say, /opt/bin? Are there problems with
"creating" new environment variables in a package installation?
To UNSUBSCRIBE, email to debian-mentors-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com
Archive: 4F143C12.firstname.lastname@example.org" target="_blank">http://lists.debian.org/4F143C12.email@example.com
Sorry for the top-posting :(