[EMAIL PROTECTED] (Bob Proulx) writes:
May I voice an opinion against a gratuitous message saying that the
behavior has changed but without real useful value? Those darn
click-throughs are a large part of the complaints against debian
packages during an install. May I suggest that if at all
[EMAIL PROTECTED] (Bob Proulx) writes:
May I voice an opinion against a gratuitous message saying that the
behavior has changed but without real useful value? Those darn
click-throughs are a large part of the complaints against debian
packages during an install. May I suggest that if at all
* Andrew Stribblehill [EMAIL PROTECTED] [021108 09:52]:
* Put a debconf message into the package warning that the behaviour
has changed. Write one init script. Allow the user to configure
which daemons start at boot-time by editing /etc/default/cfengine2
which contains RUN_CFEXECD=0;
* Andrew Stribblehill [EMAIL PROTECTED] [021108 09:52]:
* Put a debconf message into the package warning that the behaviour
has changed. Write one init script. Allow the user to configure
which daemons start at boot-time by editing /etc/default/cfengine2
which contains RUN_CFEXECD=0;
A package I maintain, cfengine2, contains three daemons, any or all
of which are useful for some people. It also has cfagent, the program
that actually does the configuration stuff it's asked to do.
At present, none of these daemons are started -- the package has no
init script, so it's up to the
Andrew == Andrew Stribblehill [EMAIL PROTECTED] writes:
Andrew * Put a debconf message into the package warning that the
Andrew behaviour has changed. Write one init script. Allow the
Andrew user to configure which daemons start at boot-time by
Andrew editing
Andrew Stribblehill [EMAIL PROTECTED] wrote:
[...]
* Put a debconf message into the package warning that the behaviour
has changed. Write one init script. Allow the user to configure
which daemons start at boot-time by editing /etc/default/cfengine2
which contains RUN_CFEXECD=0;
On Fri, Nov 08, 2002 at 03:49:27PM +, Andrew Stribblehill wrote:
A package I maintain, cfengine2, contains three daemons, any or all
of which are useful for some people. It also has cfagent, the program
that actually does the configuration stuff it's asked to do.
At present, none of
This one time, at band camp, Andrew Stribblehill wrote:
At present, none of these daemons are started -- the package has no
init script, so it's up to the user to write one, should he require
this.
I have been asked to provide an init script in a bug report. This has
the problem for me that
Andrew Stribblehill [EMAIL PROTECTED] [2002-11-08 15:49:27 +]:
I can see a number of ways out of it, but have no clear idea which is
best:
* Split the package into its component parts, such that each daemon
is in a separate package. Have an init script for each. The admin
chooses
A package I maintain, cfengine2, contains three daemons, any or all
of which are useful for some people. It also has cfagent, the program
that actually does the configuration stuff it's asked to do.
At present, none of these daemons are started -- the package has no
init script, so it's up to the
Andrew == Andrew Stribblehill [EMAIL PROTECTED] writes:
Andrew * Put a debconf message into the package warning that the
Andrew behaviour has changed. Write one init script. Allow the
Andrew user to configure which daemons start at boot-time by
Andrew editing
Andrew Stribblehill [EMAIL PROTECTED] wrote:
[...]
* Put a debconf message into the package warning that the behaviour
has changed. Write one init script. Allow the user to configure
which daemons start at boot-time by editing /etc/default/cfengine2
which contains RUN_CFEXECD=0;
On Fri, Nov 08, 2002 at 03:49:27PM +, Andrew Stribblehill wrote:
A package I maintain, cfengine2, contains three daemons, any or all
of which are useful for some people. It also has cfagent, the program
that actually does the configuration stuff it's asked to do.
At present, none of
This one time, at band camp, Andrew Stribblehill wrote:
At present, none of these daemons are started -- the package has no
init script, so it's up to the user to write one, should he require
this.
I have been asked to provide an init script in a bug report. This has
the problem for me that
Andrew Stribblehill [EMAIL PROTECTED] [2002-11-08 15:49:27 +]:
I can see a number of ways out of it, but have no clear idea which is
best:
* Split the package into its component parts, such that each daemon
is in a separate package. Have an init script for each. The admin
chooses
16 matches
Mail list logo
