Bug#183460: Updating symlinks based on new package defaults.

2010-02-20 Thread Petter Reinholdtsen
[Kurt Roeckx] > Because we don't have a way to properly update the symlinks, we > have either one of 2 situations: > - The maintainer just removes all the symlinks (remove -f) in > the maintainer scripts and then adds the new ones. This > potationaly removes configuration done by the user. Wi

Bug#183460: Updating symlinks based on new package defaults.

2010-02-20 Thread Kurt Roeckx
On Sat, Dec 26, 2009 at 10:12:57PM +0100, Kurt Roeckx wrote: > Hi, > > Because we don't have a way to properly update the symlinks, we > have either one of 2 situations: > - The maintainer just removes all the symlinks (remove -f) in > the maintainer scripts and then adds the new ones. This >

Bug#183460: Updating symlinks based on new package defaults.

2009-12-26 Thread Kurt Roeckx
Hi, Because we don't have a way to properly update the symlinks, we have either one of 2 situations: - The maintainer just removes all the symlinks (remove -f) in the maintainer scripts and then adds the new ones. This potationaly removes configuration done by the user. - Different behaviour