Yesterday, I wrote,
I understand.,, but what happens about /etc/init.d shell scripts (I
mean the ones which start, stop restart servers) ? Would be
possible to get more info about the way of manage them ?
But, this silence starts to make me think. Maybe, you want to tell me
that these
Hello, Glus.
First of all, autoconf works at build time, not install time. A particular
system, on which you install the software, may have habits different from build
system.
Second, autoconf relies on development tools, which may be not available at
install time.
And last, but not least,
I understand.,, but what happens about /etc/init.d shell scripts (I
mean the ones which start, stop restart servers) ? Would be
possible to get more info about the way of manage them ?
That is very operating system dependant, gNewSense does it one way,
Fedora another, Ubuntu yet
2009/12/15 Alfred M. Szmidt a...@gnu.org:
I understand.,, but what happens about /etc/init.d shell scripts (I
mean the ones which start, stop restart servers) ? Would be
possible to get more info about the way of manage them ?
That is very operating system dependant, gNewSense does it
Glus Xof wrote:
What should I do in my configure.ac ?... Would be necessary to make
changes in my Makefile.am ?
Apologies for perhaps excess snippage: the discussion is about
using the autotools to install in system directories.
I would make no changes to configure.ac or Makefile.am,
as
What should I do in my configure.ac ?... Would be necessary to make
changes in my Makefile.am ?
Apologies for perhaps excess snippage: the discussion is about
using the autotools to install in system directories.
I would make no changes to configure.ac or Makefile.am,
as you're looking in
But right now, I've a little problem because my server has a
configuration file. I thought that the best place to place it would
be the /etc folder... It seems that it's precisely the default
value of $(sysconfigdir), but I don't know if it's possible to my
server (my programm)
On Tue, 15 Dec 2009, Glus Xof wrote:
In this moment, I'm wonder what is, then, the purpose of make
install processes ?. I always believed that those, with root rigths,
take files and put (copy) them to the right place in the system
directories... doesn't it?
Yes, it could do that and ideally
2009/12/15 Alfred M. Szmidt a...@gnu.org:
But right now, I've a little problem because my server has a
configuration file. I thought that the best place to place it would
be the /etc folder... It seems that it's precisely the default
value of $(sysconfigdir), but I don't know if it's
2009/12/15 Bob Friesenhahn bfrie...@simple.dallas.tx.us:
On Tue, 15 Dec 2009, Glus Xof wrote:
In this moment, I'm wonder what is, then, the purpose of make
install processes ?. I always believed that those, with root rigths,
take files and put (copy) them to the right place in the system
* Glus Xof wrote on Tue, Dec 15, 2009 at 18:59 +0100:
I would make no changes to configure.ac or Makefile.am,
as you're looking in the wrong place. The type of questions
you're asking are more appropriate for the package
management system, and you should be making changes to
your spec
On Tue, 2009-12-15 at 13:02 -0500, Alfred M. Szmidt wrote:
So, Makefile should receive the value of $(sysconfigdir) from the
configuration process.
You can pass something like `-DCONFFILE=$(sysconfdir)/foo.conf' in
Makefile.am when compiling via foo_CPPFLAGS so that the program can
12 matches
Mail list logo
