Re: How to handle config file that has changed names

2003-09-22 Thread Stefano Zacchiroli
On Sun, Sep 21, 2003 at 05:25:35PM +0200, Andreas Metzler wrote: > You could conditionally move the existing configuration file in the > preinst to the new location. Thanks for your examplese. What about adding something similar to the "best packaging practice" section of the debian developer refe

Re: How to handle config file that has changed names

2003-09-22 Thread Andreas Metzler
On Sun, Sep 21, 2003 at 09:56:02PM +0100, Peter Karlsson wrote: > Andreas Metzler: > > You could conditionally move the existing configuration file in the > > preinst to the new location. > Thanks. I'm doing something similar with a non-conffile for another of > my packages, so I'll just copy the

Re: How to handle config file that has changed names

2003-09-22 Thread Stefano Zacchiroli
On Sun, Sep 21, 2003 at 05:25:35PM +0200, Andreas Metzler wrote: > You could conditionally move the existing configuration file in the > preinst to the new location. Thanks for your examplese. What about adding something similar to the "best packaging practice" section of the debian developer refe

Re: How to handle config file that has changed names

2003-09-22 Thread Andreas Metzler
On Sun, Sep 21, 2003 at 09:56:02PM +0100, Peter Karlsson wrote: > Andreas Metzler: > > You could conditionally move the existing configuration file in the > > preinst to the new location. > Thanks. I'm doing something similar with a non-conffile for another of > my packages, so I'll just copy the

Re: How to handle config file that has changed names

2003-09-21 Thread Peter Karlsson
Andreas Metzler: > You could conditionally move the existing configuration file in the > preinst to the new location. Thanks. I'm doing something similar with a non-conffile for another of my packages, so I'll just copy the working code from that. I was just unsure whether I was allowed to do it

Re: How to handle config file that has changed names

2003-09-21 Thread Peter Karlsson
Andreas Metzler: > You could conditionally move the existing configuration file in the > preinst to the new location. Thanks. I'm doing something similar with a non-conffile for another of my packages, so I'll just copy the working code from that. I was just unsure whether I was allowed to do it

Re: How to handle config file that has changed names

2003-09-21 Thread Andreas Metzler
On Sun, Sep 21, 2003 at 03:16:32PM +0100, Peter Karlsson wrote: > A new version of a package that I maintain has changed the name of the > default configuration file. I want to propagate this name change, but > how do I handle it properly? AFAICT, I'm not allowed to touch conffiles > in the maintai

How to handle config file that has changed names

2003-09-21 Thread Peter Karlsson
Hi! A new version of a package that I maintain has changed the name of the default configuration file. I want to propagate this name change, but how do I handle it properly? AFAICT, I'm not allowed to touch conffiles in the maintainer scripts, but this would mean that the old configuration would j

Re: How to handle config file that has changed names

2003-09-21 Thread Andreas Metzler
On Sun, Sep 21, 2003 at 03:16:32PM +0100, Peter Karlsson wrote: > A new version of a package that I maintain has changed the name of the > default configuration file. I want to propagate this name change, but > how do I handle it properly? AFAICT, I'm not allowed to touch conffiles > in the maintai

How to handle config file that has changed names

2003-09-21 Thread Peter Karlsson
Hi! A new version of a package that I maintain has changed the name of the default configuration file. I want to propagate this name change, but how do I handle it properly? AFAICT, I'm not allowed to touch conffiles in the maintainer scripts, but this would mean that the old configuration would j