On Sun, Feb 25, 2001 at 03:03:08PM +0100, Eric Van Buggenhaut wrote:
> That's what I read in one of your previous message and it made sense to me.
> Then Henrique argued that it was a bad idea.
>
> [...]
> > > Perhaps better: copy it in the postinst, remove the old version in the
> > > postinst.
On Sun, Feb 25, 2001 at 03:03:08PM +0100, Eric Van Buggenhaut wrote:
> That's what I read in one of your previous message and it made sense to me.
> Then Henrique argued that it was a bad idea.
>
> [...]
> > > Perhaps better: copy it in the postinst, remove the old version in the
> > > postinst.
On Sun, 25 Feb 2001, Eric Van Buggenhaut wrote:
> > > Perhaps better: copy it in the postinst, remove the old version in the
> > > postinst. Then if any problems arise, the original version will still
> > > be present.
> >
> > BAD idea. This will defeat the conffile change detection engine in dpkg
On Sun, Feb 25, 2001 at 09:34:19AM +, Julian Gilbey wrote:
> On Sun, Feb 25, 2001 at 05:15:37AM +0100, Eric Van Buggenhaut wrote:
> > > Remember to correctly unwind, moving the conffile back to its original
> > > place
> > > (as long as the original file does not exist) in the abort-install an
On Sun, 25 Feb 2001, Eric Van Buggenhaut wrote:
> > > Perhaps better: copy it in the postinst, remove the old version in the
> > > postinst. Then if any problems arise, the original version will still
> > > be present.
> >
> > BAD idea. This will defeat the conffile change detection engine in dpk
On Sun, Feb 25, 2001 at 09:34:19AM +, Julian Gilbey wrote:
> On Sun, Feb 25, 2001 at 05:15:37AM +0100, Eric Van Buggenhaut wrote:
> > > Remember to correctly unwind, moving the conffile back to its original place
> > > (as long as the original file does not exist) in the abort-install and
> >
On Sun, Feb 25, 2001 at 05:15:37AM +0100, Eric Van Buggenhaut wrote:
> > Remember to correctly unwind, moving the conffile back to its original place
> > (as long as the original file does not exist) in the abort-install and
> > abort-upgrade targets of preinst, postrm and postinst. [never tried th
On Sun, Feb 25, 2001 at 05:15:37AM +0100, Eric Van Buggenhaut wrote:
> > Remember to correctly unwind, moving the conffile back to its original place
> > (as long as the original file does not exist) in the abort-install and
> > abort-upgrade targets of preinst, postrm and postinst. [never tried t
On Sat, Feb 24, 2001 at 10:42:38PM -0300, Henrique M Holschuh wrote:
[...]
>
> Remember to correctly unwind, moving the conffile back to its original place
> (as long as the original file does not exist) in the abort-install and
> abort-upgrade targets of preinst, postrm and postinst. [never tri
On Sun, 25 Feb 2001, Julian Gilbey wrote:
> On Sat, Feb 24, 2001 at 10:42:38PM -0300, Henrique M Holschuh wrote:
> > Yes, that might be a good idea. However, as a rule of thumb, downgrading is
> > not supported (do note that failed/aborted upgrades ARE supported).
>
> It isn't? I thought we tried
On Sat, Feb 24, 2001 at 10:42:38PM -0300, Henrique M Holschuh wrote:
> On Sun, 25 Feb 2001, Julian Gilbey wrote:
> > On Fri, Feb 23, 2001 at 03:57:33PM -0800, Sean 'Shaleh' Perry wrote:
> > > in your preinst, check for /etc/foo and if it exists, mkdir /etc/package
> > > and
> >
> > Perhaps better
On Sat, Feb 24, 2001 at 10:42:38PM -0300, Henrique M Holschuh wrote:
[...]
>
> Remember to correctly unwind, moving the conffile back to its original place
> (as long as the original file does not exist) in the abort-install and
> abort-upgrade targets of preinst, postrm and postinst. [never tr
On Sun, 25 Feb 2001, Julian Gilbey wrote:
> On Fri, Feb 23, 2001 at 03:57:33PM -0800, Sean 'Shaleh' Perry wrote:
> > in your preinst, check for /etc/foo and if it exists, mkdir /etc/package and
>
> Perhaps better: copy it in the postinst, remove the old version in the
> postinst. Then if any prob
On Fri, Feb 23, 2001 at 03:57:33PM -0800, Sean 'Shaleh' Perry wrote:
> in your preinst, check for /etc/foo and if it exists, mkdir /etc/package and
> copy /etc/foo there. Then remove /etc/foo. Import thing here is that the
> preinst should not die because of any errors here.
Perhaps better: copy
On Sun, 25 Feb 2001, Julian Gilbey wrote:
> On Sat, Feb 24, 2001 at 10:42:38PM -0300, Henrique M Holschuh wrote:
> > Yes, that might be a good idea. However, as a rule of thumb, downgrading is
> > not supported (do note that failed/aborted upgrades ARE supported).
>
> It isn't? I thought we trie
On Sat, Feb 24, 2001 at 10:42:38PM -0300, Henrique M Holschuh wrote:
> On Sun, 25 Feb 2001, Julian Gilbey wrote:
> > On Fri, Feb 23, 2001 at 03:57:33PM -0800, Sean 'Shaleh' Perry wrote:
> > > in your preinst, check for /etc/foo and if it exists, mkdir /etc/package and
> >
> > Perhaps better: copy
On Sun, 25 Feb 2001, Julian Gilbey wrote:
> On Fri, Feb 23, 2001 at 03:57:33PM -0800, Sean 'Shaleh' Perry wrote:
> > in your preinst, check for /etc/foo and if it exists, mkdir /etc/package and
>
> Perhaps better: copy it in the postinst, remove the old version in the
> postinst. Then if any pro
On Fri, Feb 23, 2001 at 03:57:33PM -0800, Sean 'Shaleh' Perry wrote:
> in your preinst, check for /etc/foo and if it exists, mkdir /etc/package and
> copy /etc/foo there. Then remove /etc/foo. Import thing here is that the
> preinst should not die because of any errors here.
Perhaps better: cop
Colin Watson dijo:
> You have to be even more careful than that, since the installation might fail
> and dpkg might want to unwind the maintainer scripts - so 'postrm
> abort-upgrade' and 'postrm abort-install' need to move the file back if
> possible.
Thanks a lot. I had not taken that into accou
Colin Watson dijo:
> You have to be even more careful than that, since the installation might fail
> and dpkg might want to unwind the maintainer scripts - so 'postrm
> abort-upgrade' and 'postrm abort-install' need to move the file back if
> possible.
Thanks a lot. I had not taken that into acco
"Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> wrote:
>On 23-Feb-2001 Amaya wrote:
>> Of course not! ;-) I'd just move them to the new location.
>> But, I'm starting to think this is not a good idea, maybe.
>
>after talking with other devels here is a method:
>
>in your preinst, check for /etc/foo and i
"Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> wrote:
>On 23-Feb-2001 Amaya wrote:
>> Of course not! ;-) I'd just move them to the new location.
>> But, I'm starting to think this is not a good idea, maybe.
>
>after talking with other devels here is a method:
>
>in your preinst, check for /etc/foo and
On 23-Feb-2001 Amaya wrote:
> Sean 'Shaleh' Perry dijo:
>> how will this affect current users of your package? when they upgrade, will
>> they lose all of their old settings?
>
> Of course not! ;-) I'd just move them to the new location.
> But, I'm starting to think this is not a good idea, mayb
Sean 'Shaleh' Perry dijo:
> how will this affect current users of your package? when they upgrade, will
> they lose all of their old settings?
Of course not! ;-) I'd just move them to the new location.
But, I'm starting to think this is not a good idea, maybe.
--
If you don't spend energy get
>> Problem is, you can only declare a conffile if it is in your package. So you
>> new package has /etc/package/foo and it used to be /etc/foo. What happens
>> to
>> /etc/foo? What happens to its configuration changes the admin made?
>
> Let's just move conffiles to the new location then... I ha
Sean 'Shaleh' Perry dijo:
> it is difficult to move conffiles, why do you think they should be in
> /etc/my_package?
I just think it's cleaner.
> Problem is, you can only declare a conffile if it is in your package. So you
> new package has /etc/package/foo and it used to be /etc/foo. What happe
On 23-Feb-2001 Amaya wrote:
> Sean 'Shaleh' Perry dijo:
>> how will this affect current users of your package? when they upgrade, will
>> they lose all of their old settings?
>
> Of course not! ;-) I'd just move them to the new location.
> But, I'm starting to think this is not a good idea, may
Sean 'Shaleh' Perry dijo:
> how will this affect current users of your package? when they upgrade, will
> they lose all of their old settings?
Of course not! ;-) I'd just move them to the new location.
But, I'm starting to think this is not a good idea, maybe.
--
If you don't spend energy ge
On 23-Feb-2001 Amaya wrote:
> I have recently adopted a package that places two conffiles in /etc/
> I think that it would be more appropiate to place them under /etc/my_package/
> I need some help regarding how to do it and if it should be done at all.
>
> Thanks a lot in advance.
>
it is diff
>> Problem is, you can only declare a conffile if it is in your package. So you
>> new package has /etc/package/foo and it used to be /etc/foo. What happens
>> to
>> /etc/foo? What happens to its configuration changes the admin made?
>
> Let's just move conffiles to the new location then... I h
Sean 'Shaleh' Perry dijo:
> it is difficult to move conffiles, why do you think they should be in
> /etc/my_package?
I just think it's cleaner.
> Problem is, you can only declare a conffile if it is in your package. So you
> new package has /etc/package/foo and it used to be /etc/foo. What happ
On 23-Feb-2001 Amaya wrote:
> I have recently adopted a package that places two conffiles in /etc/
> I think that it would be more appropiate to place them under /etc/my_package/
> I need some help regarding how to do it and if it should be done at all.
>
> Thanks a lot in advance.
>
it is dif
32 matches
Mail list logo
