On Tue, Jul 12, 2005 at 12:42:38PM +0200, Loïc Minier wrote: > On mar, jui 12, 2005, Steve Langasek wrote: > > This could be fixed in libct3 by creating a separate package just to hold > > the config file, but that isn't even an issue until the next time libct's > > soname changes.
> Would libct3 conflict / replace libct1, I think this wouldn't happen, > would it? > Currently it's something like: > 1 unpack libct3 > 2 purge libct1 > 3 remove lict1 > 4 configure libct3 > (Or maybe it's 1, 2, 4, 3.) No, purge *always* happens after remove; a conflicts could ensure removal of libct1 before unpacking of libct3, but it could not ensure purging of libct1 before unpacking of libct3. > Anyway, the mkdir I suggested is helpful as it permits to go through > the process, even if it hides the problem, and it serves robustness I > believe. Sure, I agree with that. -- Steve Langasek postmodern programmer
