script as a configuration file

Hello, I was seeking for some opinions... I'm working now on a package that relies on a script that may be modified by the system administrator, and I'm wondering about: - how to manage upgrades (overwrites & co.) - where to put it This script works well with a default debian installt

Re: script as a configuration file

At 9:10 +0200 9/27/02, Carlo Contavalli wrote: >Hello, > > I was seeking for some opinions... I'm working now on a >package that relies on a script that may be modified by the system >administrator, and I'm wondering about: > > - how to manage upgrades (overwrites & co.) > - where to put it >

Re: script as a configuration file

On Fri, Sep 27, 2002 at 09:10:21AM +0200, Carlo Contavalli wrote: >I was seeking for some opinions... I'm working now on a > package that relies on a script that may be modified by the system > administrator, and I'm wondering about: > > - how to manage upgrades (overwrites & co.) > - wh

script as a configuration file

Hello, I was seeking for some opinions... I'm working now on a package that relies on a script that may be modified by the system administrator, and I'm wondering about: - how to manage upgrades (overwrites & co.) - where to put it This script works well with a default debian installti

Re: script as a configuration file

At 9:10 +0200 9/27/02, Carlo Contavalli wrote: >Hello, > > I was seeking for some opinions... I'm working now on a >package that relies on a script that may be modified by the system >administrator, and I'm wondering about: > > - how to manage upgrades (overwrites & co.) > - where to put it > >

Re: script as a configuration file

On Fri, Sep 27, 2002 at 09:10:21AM +0200, Carlo Contavalli wrote: >I was seeking for some opinions... I'm working now on a > package that relies on a script that may be modified by the system > administrator, and I'm wondering about: > > - how to manage upgrades (overwrites & co.) > - whe