View Single Post
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#2
You should be able to flag the files as configuration files to prevent them being replaced - see http://www.debian.org/doc/debian-pol...conffiles.html

As for the database updates - either 1 or 2 would work. It may depend on whether any user interaction would be required for the updates (e.g. to ask for default values for a new column), in which case #1 would definitely be better. You'd also have to make sure that whatever process you use can deal with updating across multiple versions (as users may not install all intervening versions).
 

The Following 3 Users Say Thank You to Rob1n For This Useful Post: