Santiago == Santiago Vila [EMAIL PROTECTED] writes:
* configuration files for which it is impossible to find a
common file that works for every user should not be part of the
filesystem archive inside the .deb package, so that dpkg will
not prompt the user again and again
Brian White:
[ Kai: ]
We should also correct the policy to say that _no_ package should touch
_any_ config file from a script. The problem caused that way isn't related
to which package script and config file belong to.
While a good general rule, I think it would be a mistake to make it
On Mon, 2 Feb 1998, Ian Jackson wrote:
Brian White:
[ Kai: ]
We should also correct the policy to say that _no_ package should touch
_any_ config file from a script. The problem caused that way isn't related
to which package script and config file belong to.
While a good general
-BEGIN PGP SIGNED MESSAGE-
On Mon, 2 Feb 1998, Christian Schwarz wrote:
Is the following solution correct?
1. The `conffile' is _not_ tagged as conffile and _not_ included in the
package tree,
2. it's created in the postinst script if that file does not already
exist,
3. it's
-BEGIN PGP SIGNED MESSAGE-
On Mon, 2 Feb 1998, I wrote:
``[...] It is almost certain that any file in /etc that is in your
package's filesystem archive should be listed in dpkg's conffiles control
area file. (See the Debian Packaging Manual).
It is almost certain that any file
[EMAIL PROTECTED] (Brian White) wrote on 15.01.98 in [EMAIL PROTECTED]:
The current policy does not allow packages to touch /etc/crontab
anymore. This is because we don't allow packages to modify other
packages configuration files.
We should also correct the policy to say that _no_
The current policy does not allow packages to touch /etc/crontab anymore.
This is because we don't allow packages to modify other packages
configuration files.
We should also correct the policy to say that _no_ package should touch
_any_ config file from a script. The problem caused that
On Tue, Jan 13, 1998 at 11:34:23PM +0100, Christian Schwarz wrote:
Since a few packages have to register cron jobs which need to be run more
often than `daily', the cron package has been changed to read all files in
/etc/cron.d too and interpret these as additions to /etc/crontab. With that,
[EMAIL PROTECTED] (Christian Schwarz) wrote on 13.01.98 in [EMAIL PROTECTED]:
The current policy does not allow packages to touch /etc/crontab anymore.
This is because we don't allow packages to modify other packages
configuration files.
We should also correct the policy to say that _no_
[This mail is part of Debian Policy Weekly issue #5]
Topic 3: How packages can register cron jobs
STATE: APPROVAL
The current policy does not allow packages to touch /etc/crontab anymore.
This is because we don't allow packages to modify other packages
configuration files.
Thus, currently
10 matches
Mail list logo
