On Wed, Feb 01, 2023 at 01:56:20PM +0100, Milan Crha wrote: > 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 > migration, aka the app cannot read both formats, it can use one or the > other. ...snip... > > I'm sure you might find more disadvantages, these are just the top > four. > > 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. > > Still, how does other packages migrate their data, or at least help the > users with the migration? Is there any way? Modifying users home directories is explicitly against packagin guidelines. ;( https://docs.fedoraproject.org/en-US/packaging-guidelines/#_no_files_or_directories_under_srv_usrlocal_or_homeuser Is there any way to pull the functionaly into the process itself? ie, the first time it's called, it converts the db? (But that might make it really slow on the first call). Or perhaps it just warns there and points to the script the user can run to do the conversion? I suppose there's the way postgresql does it... including a copy of the old server binaries that can read the old format in the new rpm so it can use that to convert to the new format? kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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
