-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thijs Kinkhorst wrote:
> On Sunday 16 March 2008 19:42, Christian Perrier wrote:
>> An easy and not too much invasive fix would be to copy the file in /root
>> instead of /tmp.
> 
> I'm quite unsure that writing to /root upon purge is a good idea.
> 
> If you really need to retain those settings to purge, better do it this way:
> 1) In prerm, copy /etc/axyl/axyl.conf to /etc/axyl/axyl.conf.backup
> 2) In postrm, source that file.
> 3) In postrm, rm /etc/axyl/axyl.conf.backup && rmdir /etc/axyl/
> 
> But I doubt that it's useful to retain those settings at postrm as has been 
> indicated by others in this bug already. As you source the file, what happens 
> in a scenario where the admin has a syntax error in axyl.conf and then purges 
> it? The purge will fail with an error, also not so nice.
> 
>> It should be noted that, having looked just now, I can't actually find
>> official policy on this concept of purging absolutely *everything* in this
>> way, so I'm not sure what the piuparts errors were based on.
> 
> It's rather undefined in policy what exactly should be purged, unfortunately.
> 
>> If full purge isn't official policy, then the quick fix would be to remove
>> this functionality entirely for now, and I'd be quite happy to do that.
> 
> I propose to just remove every dir we installed and let the admin take care 
> of 
> whatever extra dirs he added. That seems in spirit of Debian policy: clean up 
> what we install, and don't touch things outside of it.
> 
> That would also mean that piuparts would not complain, since that does not 
> add 
> dirs to axyl.conf itself, does it?


That's correct. In the tests it uses the default locations. My purge was
designed to just get rid of Axyl home, data, logs wherever the admin had
decided to put them in the debconf config (or perhaps moved them
manually afterwards).

But I will now be implementing the proposition above, which will remove
the need to save axyl.conf across prerm --> postrm.

Thanks for all the great ideas and feedback.

Cheers,
Paul.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH3sXntfkpAgkMOyMRAtmbAJ9QBYal2Q5k9YB89Z25F+mB45diLgCfU+uL
3ypfEITzBrVVvwf/mf/oO+s=
=D/uX
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to