Hi, sorry for the big delay in my answer.
On Sat, 01 Dec 2012, Gregor Jasny wrote: > There are some open questions on my side: > 1) Do you see a demand to also require a LASTVERSION argument? Yes. We always want to restrict such code to be only executed when really needed. Think for example when you have an history where you switched a path back and forth between a directory and a symlink. You don't want to execute both commands for any upgrade... > 2) Shold I also check where $SYMLINK.dpkg-remove is pointing to in the > post* scripts? I don't see the need for this. > 3) Is there a testbed where I can add tests for this? We have a pkg-tests.git repository, see explanations in http://wiki.debian.org/Teams/Dpkg/Contribute There are already some tests for dpkg-maintscript-helper in it. > 4) What about downgrading packages? Would that be an use case, too? Yes. I always try to take it into account in dpkg-maintscript-helper. That said I would not make it a requirement to merge this new command. But this alone justifies the LASTVERSION parameter, so that downgrade support can at least be implemented... > + if [ "$1" = "install" -o "$1" = "upgrade" ] && [ -n "$2" ] && [ > -L "$SYMLINK" ] && [ "$(readlink "$SYMLINK")" = "$SYMLINK_TARGET" ]; then > + mv -f "$SYMLINK" "$SYMLINK.dpkg-remove" Please do not use "-L" but "-h" (-L is non-standard). Otherwise it looks like a good start. Thanks for trying to tackle this! Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
