Julian Gilbey <[EMAIL PROTECTED]> writes:
> On Tue, Oct 16, 2001 at 10:46:52PM -0600, Matt Armstrong wrote:
>
> Who needs to edit it, the sysadmin or the maintainer scripts?
>
>> - I really do want to make it a conffile, so the user is notified of
>> future options.
>
> There are other
Julian Gilbey <[EMAIL PROTECTED]> writes:
> On Tue, Oct 16, 2001 at 10:46:52PM -0600, Matt Armstrong wrote:
>
> Who needs to edit it, the sysadmin or the maintainer scripts?
>
>> - I really do want to make it a conffile, so the user is notified of
>> future options.
>
> There are othe
On Tue, Oct 16, 2001 at 10:46:52PM -0600, Matt Armstrong wrote:
> I'm packaging my own program (http://www.lickey.com/flipit/) and have a
> question about configuration files.
>
> So I'm left in a situation where:
>
> - Policy forbids me from editing the /etc/flipit.conf if I mark it a
>
On Tue, Oct 16, 2001 at 10:46:52PM -0600, Matt Armstrong wrote:
> I'm packaging my own program (http://www.lickey.com/flipit/) and have a
> question about configuration files.
>
> So I'm left in a situation where:
>
> - Policy forbids me from editing the /etc/flipit.conf if I mark it a
>
Matt Armstrong wrote:
> - I really do want to make it a conffile, so the user is notified of
> future options.
I don't follow this point. The user will only be informed that the
conffile has changed if they have modified it in some way and you change
the conffile that's distributed with
Russell Coker wrote:
> OK. So you install a file and then customise it to the user. IMHO
> customising the file on first install does not count as "editing a conf file"
> as you are just changing what the user will see as the default config.
In your opinion mabe, but not according to policy. A
On Wed, 17 Oct 2001 06:46, Matt Armstrong wrote:
> - Policy forbids me from editing the /etc/flipit.conf if I mark it a
> conffile.
> - The program won't work if /etc/flipit.conf isn't edited.
> - I really do want to make it a conffile, so the user is notified of
> future op
Matt Armstrong wrote:
> - I really do want to make it a conffile, so the user is notified of
> future options.
I don't follow this point. The user will only be informed that the
conffile has changed if they have modified it in some way and you change
the conffile that's distributed with
Russell Coker wrote:
> OK. So you install a file and then customise it to the user. IMHO
> customising the file on first install does not count as "editing a conf file"
> as you are just changing what the user will see as the default config.
In your opinion mabe, but not according to policy.
On Wed, 17 Oct 2001 06:46, Matt Armstrong wrote:
> - Policy forbids me from editing the /etc/flipit.conf if I mark it a
> conffile.
> - The program won't work if /etc/flipit.conf isn't edited.
> - I really do want to make it a conffile, so the user is notified of
> future o
>
> So I'm left in a situation where:
>
> - Policy forbids me from editing the /etc/flipit.conf if I mark it a
> conffile.
> - The program won't work if /etc/flipit.conf isn't edited.
> - I really do want to make it a conffile, so the user is notified of
> future options.
11 matches
Mail list logo