On Wed, 14 May 2003 09:36:57 -0700, Keegan Quinn <[EMAIL PROTECTED]> said:
>> The only solution I think is if dpkg were to take over
>> responsibility for deleting configuration files, so that the postrm
>> script doesn't have to worry.
> I think that in this situation, package a should check if a-beta is
> installed during its postrm purge, and avoid taking over... Is
> there some reason you think this doesn't work?
What if I am not aware of a-beta? What if a-beta does not
exist when package a was created? What if there are several a-betas,
and I miss a few?
manoj
--
Don't be irreplaceable, if you can't be replaced, you can't be
promoted.
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
