Dne 01. 02. 23 v 13:56 Milan Crha napsal(a):
Hi,
this is a query for an opinion and a best-practice experience for a
case when a package needs to change its internal database format
between versions, in an environment, which does not allow real
....
That being said, any such change surely deserves release notes, with
the commands what to do to export and then back import the wordlist.
There should be filled a corresponding Change too, I guess.
Yes. Likely both. If you will go the release notes only way then open the issue here
https://pagure.io/fedora-docs/release-notes
But I strongly encourage you to create Change proposal as it gives you a lot of advertisment and therefore awareness for
free.
Still, how does other packages migrate their data, or at least help the
users with the migration? Is there any way?
Put aside all your expectation. The reality will always surprise you no matter how big is your imagination.
I worked in past on project where the DB was sometimes huge. And upgrades of the schema took 20+ hours even on beefy
machines. The stories...
The best practice is to document it. Announce in advance. And when package is upgraded flip some variable in config
(/etc/sysconfig/$package or ~/.config/$package) and until user flip the variable back, do not start the
service/application and if user attempts to start it, exit with message like:
The DB schema of $package changed. Please migrate to new format using a tool `$migration-tool`. And then change variable
FOO in /etc/sysconfig/$package
For more information see $URL
Miroslav
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
