* Jose-Marcio wrote on Mon, Jul 28, 2008 at 05:27:00PM CEST:
>
> In fact, the real reason, for me, to have another target, is to reuse
> some configuration values defined during "configure" run, such as
> prefix, all dirs (sysconfdir, datadir, sbindir, ... ). Maybe it could be
> interesting t
Hello Ralf,
Ralf Wildenhues wrote:
* Jose-Marcio wrote on Mon, Jul 21, 2008 at 04:46:29PM CEST:
Well, one reason I'm hesitant is that I think most such pre- or post-
actions are pretty system-dependent, more so than other tasks routinely
done in makefiles. For example, they would often dep
* Jose-Marcio wrote on Mon, Jul 21, 2008 at 04:46:29PM CEST:
> Ralf Wildenhues wrote:
>>
>> upgrade:
>> $(MAKE) $(AM_MAKEFLAGS) preinstall
>> $(MAKE) $(AM_MAKEFLAGS) install
>> $(MAKE) $(AM_MAKEFLAGS) postinstall
> Only to let you know. Maybe other people have the same needs than
Hi,
Ralf Wildenhues wrote:
Hello,
usefully. What you can do instead is
upgrade:
$(MAKE) $(AM_MAKEFLAGS) preinstall
$(MAKE) $(AM_MAKEFLAGS) install
$(MAKE) $(AM_MAKEFLAGS) postinstall
Thanks. Good ! I'll do this way.
...
I'm not sure whether we should introd
Hello,
* Bernd Jendrissek wrote on Fri, Jul 18, 2008 at 01:32:34PM CEST:
> On Thu, Jul 17, 2008 at 10:20 AM, Jose-Marcio <[EMAIL PROTECTED]> wrote:
> > Currently, I've defined a new target (upgrade) which depends
> > on :
> >
> > upgrade : preinstall install postinstall
>
> Note that that breaks
On Thu, Jul 17, 2008 at 10:20 AM, Jose-Marcio <[EMAIL PROTECTED]> wrote:
> Currently, I've defined a new target (upgrade) which depends
> on :
>
> upgrade : preinstall install postinstall
Note that that breaks under make -j upgrade.
> Is there a more elegant way to do this ?
I think it's about a
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
