Re: /etc/ question
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. Then if any problems arise, the original version will still be present. BAD idea. This will defeat the conffile change detection engine in dpkg, and will cause problems in some cases. Don't do that. Did he just say that because of the typo ? s/postinst/preinst ? I'm sure it was; copying it in the preinst will allow dpkg to do its work. But remember someone else's advice: copy iff old conffile exists and new conffile doesn't. It's probably not a disaster if the upgrade bombs and the new conffile is left in place; you may not even need to worry about error unwinding. Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London Debian GNU/Linux Developer, see http://people.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /etc/ question
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. Then if any problems arise, the original version will still be present. BAD idea. This will defeat the conffile change detection engine in dpkg, and will cause problems in some cases. Don't do that. Did he just say that because of the typo ? s/postinst/preinst ? I'm sure it was; copying it in the preinst will allow dpkg to do its work. But remember someone else's advice: copy iff old conffile exists and new conffile doesn't. It's probably not a disaster if the upgrade bombs and the new conffile is left in place; you may not even need to worry about error unwinding. Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London Debian GNU/Linux Developer, see http://people.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/
Re: /etc/ question
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 abort-upgrade targets of preinst, postrm and postinst. [never tried this, but that seems to be what's needed from the not-so-clear policy chapter 6] In the package I maintain, called crafty, I moved /etc/craftyrc to /etc/crafty.rc and /var/cache/crafty to /var/lib/crafty in the previous version (17.9). Version now is 17.13. The 'move' routine is still in preinst of the latest version because we don't know what version people are upgrading from. Now that's my problem : if upgrade fails or is aborted, I should move the files back to their original location. But if people are upgrading from a 'post-move' version, the original location is different than if they were upgrading from a 'pre-move' location. So, where do I move the files back ??? Copy in the preinst, remove the old one in the postinst (with "configure" argument). That'll do the job. 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. 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 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, and will cause problems in some cases. Don't do that. Did he just say that because of the typo ? s/postinst/preinst ? Henrique ? Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London Debian GNU/Linux Developer, see http://people.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/ -- Eric VAN BUGGENHAUT [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /etc/ question
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, and will cause problems in some cases. Don't do that. Did he just say that because of the typo ? s/postinst/preinst ? Yes. As long as the copy/move is done in preinst, it will not cause problems with the conffile handling by dpkg. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh PGP signature
Re: /etc/ question
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 this, but that seems to be what's needed from the not-so-clear policy chapter 6] In the package I maintain, called crafty, I moved /etc/craftyrc to /etc/crafty.rc and /var/cache/crafty to /var/lib/crafty in the previous version (17.9). Version now is 17.13. The 'move' routine is still in preinst of the latest version because we don't know what version people are upgrading from. Now that's my problem : if upgrade fails or is aborted, I should move the files back to their original location. But if people are upgrading from a 'post-move' version, the original location is different than if they were upgrading from a 'pre-move' location. So, where do I move the files back ??? Copy in the preinst, remove the old one in the postinst (with configure argument). That'll do the job. Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London Debian GNU/Linux Developer, see http://people.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/
Re: /etc/ question
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 abort-upgrade targets of preinst, postrm and postinst. [never tried this, but that seems to be what's needed from the not-so-clear policy chapter 6] In the package I maintain, called crafty, I moved /etc/craftyrc to /etc/crafty.rc and /var/cache/crafty to /var/lib/crafty in the previous version (17.9). Version now is 17.13. The 'move' routine is still in preinst of the latest version because we don't know what version people are upgrading from. Now that's my problem : if upgrade fails or is aborted, I should move the files back to their original location. But if people are upgrading from a 'post-move' version, the original location is different than if they were upgrading from a 'pre-move' location. So, where do I move the files back ??? Copy in the preinst, remove the old one in the postinst (with configure argument). That'll do the job. 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. 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 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, and will cause problems in some cases. Don't do that. Did he just say that because of the typo ? s/postinst/preinst ? Henrique ? Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London Debian GNU/Linux Developer, see http://people.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/ -- Eric VAN BUGGENHAUT [EMAIL PROTECTED]
Re: /etc/ question
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, and will cause problems in some cases. Don't do that. Did he just say that because of the typo ? s/postinst/preinst ? Yes. As long as the copy/move is done in preinst, it will not cause problems with the conffile handling by dpkg. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh pgpnyMfyIIxPq.pgp Description: PGP signature
Re: /etc/ question
"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 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. Your package contains /etc/package/foo. When dpkg gets to the point where the conffile will be installed, it will do the usual checking if the conffile should be changed and prompting the user. 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. -- Colin Watson [[EMAIL PROTECTED]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /etc/ question
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 account 0:-) -- If you don't spend energy getting what you want, you'll have to spend it dealing with what you get. - Unknown Proudly running Debian GNU/Linux Sid (Kernel 2.2.17) on this Dell Laptop PGP signature
Re: /etc/ question
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 it in the postinst, remove the old version in the postinst. Then if any problems arise, the original version will still be present. If you are really careful, you should also move them back if the package is being downgraded to a pre-move version. Check policy to see how the maintainer scripts are run. Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London Debian GNU/Linux Developer, see http://people.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /etc/ question
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 problems arise, the original version will still be present. BAD idea. This will defeat the conffile change detection engine in dpkg, and will cause problems in some cases. Don't do that. In the *pre*inst, mv old - new IFF old exists and new does NOT exist In the posinst, just use the new location. 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 this, but that seems to be what's needed from the not-so-clear policy chapter 6] If you are really careful, you should also move them back if the package is being downgraded to a pre-move version. Check policy to see how the maintainer scripts are run. 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). -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh PGP signature
Re: /etc/ question
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 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, and will cause problems in some cases. Don't do that. Oops, typo! Thanks for spotting it. Read as follows: Perhaps better: copy it in the PREINST, remove the old version in the postinst. Then if any problems arise, the original version will still be present. In the *pre*inst, mv old - new IFF old exists and new does NOT exist Good. In the posinst, just use the new location. 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 this, but that seems to be what's needed from the not-so-clear policy chapter 6] Agreed it's not so clear. I want to figure out what questions to ask Wichert about what it says. I'm confused about when error unwinding is done and would like to clarify it. If you are really careful, you should also move them back if the package is being downgraded to a pre-move version. Check policy to see how the maintainer scripts are run. 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 to as much as possible. Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London Debian GNU/Linux Developer, see http://people.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /etc/ question
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 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. Your package contains /etc/package/foo. When dpkg gets to the point where the conffile will be installed, it will do the usual checking if the conffile should be changed and prompting the user. 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. -- Colin Watson [EMAIL PROTECTED]
Re: /etc/ question
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 account 0:-) -- If you don't spend energy getting what you want, you'll have to spend it dealing with what you get. - Unknown Proudly running Debian GNU/Linux Sid (Kernel 2.2.17) on this Dell Laptop pgpGSnZlFVB38.pgp Description: PGP signature
Re: /etc/ question
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 it in the postinst, remove the old version in the postinst. Then if any problems arise, the original version will still be present. If you are really careful, you should also move them back if the package is being downgraded to a pre-move version. Check policy to see how the maintainer scripts are run. Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London Debian GNU/Linux Developer, see http://people.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/
Re: /etc/ question
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 problems arise, the original version will still be present. BAD idea. This will defeat the conffile change detection engine in dpkg, and will cause problems in some cases. Don't do that. In the *pre*inst, mv old - new IFF old exists and new does NOT exist In the posinst, just use the new location. 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 this, but that seems to be what's needed from the not-so-clear policy chapter 6] If you are really careful, you should also move them back if the package is being downgraded to a pre-move version. Check policy to see how the maintainer scripts are run. 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). -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh pgpqPVwuSaVSu.pgp Description: PGP signature
Re: /etc/ question
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 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, and will cause problems in some cases. Don't do that. Oops, typo! Thanks for spotting it. Read as follows: Perhaps better: copy it in the PREINST, remove the old version in the postinst. Then if any problems arise, the original version will still be present. In the *pre*inst, mv old - new IFF old exists and new does NOT exist Good. In the posinst, just use the new location. 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 this, but that seems to be what's needed from the not-so-clear policy chapter 6] Agreed it's not so clear. I want to figure out what questions to ask Wichert about what it says. I'm confused about when error unwinding is done and would like to clarify it. If you are really careful, you should also move them back if the package is being downgraded to a pre-move version. Check policy to see how the maintainer scripts are run. 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 to as much as possible. Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London Debian GNU/Linux Developer, see http://people.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/
Re: /etc/ question
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 to as much as possible. Try is the operative word. Don't do that to anything you can't risk being left as a complete mess. Downgrading glibc has killed more than one with extreme prejudice, I'm told :P -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh pgptpEcfPicAv.pgp Description: PGP signature
Re: /etc/ question
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 tried this, but that seems to be what's needed from the not-so-clear policy chapter 6] In the package I maintain, called crafty, I moved /etc/craftyrc to /etc/crafty.rc and /var/cache/crafty to /var/lib/crafty in the previous version (17.9). Version now is 17.13. The 'move' routine is still in preinst of the latest version because we don't know what version people are upgrading from. Now that's my problem : if upgrade fails or is aborted, I should move the files back to their original location. But if people are upgrading from a 'post-move' version, the original location is different than if they were upgrading from a 'pre-move' location. So, where do I move the files back ??? -- Eric VAN BUGGENHAUT [EMAIL PROTECTED]
/etc/ question
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. -- If you don't spend energy getting what you want, you'll have to spend it dealing with what you get. - Unknown Proudly running Debian GNU/Linux Sid (Kernel 2.2.17) on this Dell Laptop -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /etc/ question
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 happens to /etc/foo? What happens to its configuration changes the admin made? Let's just move conffiles to the new location then... I have seen it in sendmail and other packages. But, anyway... is it really a good idea? -- If you don't spend energy getting what you want, you'll have to spend it dealing with what you get. - Unknown Proudly running Debian GNU/Linux Sid (Kernel 2.2.17) on this Dell Laptop PGP signature
Re: /etc/ question
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 have seen it in sendmail and other packages. But, anyway... is it really a good idea? how will this affect current users of your package? when they upgrade, will they lose all of their old settings? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /etc/ question
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 getting what you want, you'll have to spend it dealing with what you get. - Unknown Proudly running Debian GNU/Linux Sid (Kernel 2.2.17) on this Dell Laptop PGP signature
Re: /etc/ question
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, maybe. after talking with other devels here is a method: 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. Your package contains /etc/package/foo. When dpkg gets to the point where the conffile will be installed, it will do the usual checking if the conffile should be changed and prompting the user. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
/etc/ question
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. -- If you don't spend energy getting what you want, you'll have to spend it dealing with what you get. - Unknown Proudly running Debian GNU/Linux Sid (Kernel 2.2.17) on this Dell Laptop
RE: /etc/ question
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 difficult to move conffiles, why do you think they should be in /etc/my_package? 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?
Re: /etc/ question
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 happens to /etc/foo? What happens to its configuration changes the admin made? Let's just move conffiles to the new location then... I have seen it in sendmail and other packages. But, anyway... is it really a good idea? -- If you don't spend energy getting what you want, you'll have to spend it dealing with what you get. - Unknown Proudly running Debian GNU/Linux Sid (Kernel 2.2.17) on this Dell Laptop pgpxsD3snJYIp.pgp Description: PGP signature
Re: /etc/ question
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 have seen it in sendmail and other packages. But, anyway... is it really a good idea? how will this affect current users of your package? when they upgrade, will they lose all of their old settings?
Re: /etc/ question
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 getting what you want, you'll have to spend it dealing with what you get. - Unknown Proudly running Debian GNU/Linux Sid (Kernel 2.2.17) on this Dell Laptop pgpNQt64NQRXH.pgp Description: PGP signature
Re: /etc/ question
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, maybe. after talking with other devels here is a method: 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. Your package contains /etc/package/foo. When dpkg gets to the point where the conffile will be installed, it will do the usual checking if the conffile should be changed and prompting the user.
