Hi! I want to pick your brains about something, if I may. How do you handle a port update (like eg. postgresql) as a maintainer, if the new version is not compatible with the older versions' data files? I can see that with every major version postgresql update, there is a warning to dump/restore. But it always seemed futile to me to display a warning that a dump would have been necessary, after that fact that the package has been upgraded (and I don't the old binaries). Of course, this port (kc) is not at all that much widely used as postgresql, but still, I would like to make the transition as painless as possible. Surely, if one installs the new version, and then recognizes that the database file can not be opened -- and it should've been dumped so it could be imported to the new version --, it is not much of a consolation to read about this in the package's post-install message.
What do you reckon? Thanks, Daniel -- LÉVAI Dániel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
