So in writing test scripts, I happened to read the man page for sh, and
in APPLICATION USAGE it mentions that
"Applications should note that the standard PATH to the shell cannot be
assumed to be either /bin/sh or /usr/bin/sh, and should be determined by
interrogation of the PATH returned by getcon
Automake doesn't really know how to deal with python. I have come across
a lot of cross compilation problems.
When cross compiling an app there is currently no way of determining
a) which python headers are suitable for the target platform.
b) what version of python is available on the tar
Hello,
Is there a way to define pre and post install actions ?
My problem is :
I have an application which is a daemon which uses some flavor
of databases (BerkeleyDB, in fact).
When installing a new version of the application, I'd like to be
able to stop the daemon, eventually dump databases
Ralf Wildenhues wrote:
* Ralf Wildenhues wrote on Wed, Jul 16, 2008 at 11:39:00PM CEST:
Is there a proper automake way of installing startup scripts?
Try
init_d_dir = $(sysconfdir)/rc.d/init.d
init_d_dir_SCRIPTS = blah
The last line should've been
init_d_SCRIPTS = blah
