On Tue, Oct 01, 2002 at 10:26:18AM +0200, Erich Schubert wrote: > > Number one is most admin friendly, yet if the package maintainer screws > Well, i think number 3 is even more admin friendly. But a lot of work > for the maintainer usually. Maybe we should think about changing that? It would probably be possible to set up things so that a package could drop an "upgrade" or "cleanup" script into a directory somewhere, and arrange for users' "xsessions" and "profiles" to check for new scripts in that directory to run. It might be an idea to adapt debconf for this, so that it doesn't matter so much whether you start up in X or login over ssh -- you can end up with a GUI or a tty interface as appropriate. Maybe: Template: mozilla/$user/upgrade-from-M16 ... and #!/bin/sh db_fget mozilla/$user/upgrade-from-M16 seen if [ "$RET" = true ]; then exit 0 fi db_fset mozilla/$user/upgrade-from-M16 seen true # ask any questions needed, fixup the config with every single one of those things rerun everytime you login. It'd probably work, there're probably other better ways of doing it, and whether it's worth doing at all is probably questionable too. Ultimately, it'd be the users' responsibility to run these scripts at all, but we ought to be able to make it easy for the admin to make that default correctly fairly easily. Cheers, aj -- Anthony Towns <email@example.com> <http://azure.humbug.org.au/~aj/> I don't speak for anyone save myself. GPG signed mail preferred. ``If you don't do it now, you'll be one year older when you do.''
Description: PGP signature