#2914: Config migration, file format and default config
-------------------+----------------------------
Reporter: bro | Owner:
Type: bug | Status: new
Priority: minor | Milestone: needs verified
Component: Core | Version: develop (git)
Keywords: |
-------------------+----------------------------
The current config system supports registering migration functions to
migrate old configs to new formats. I migration function will migrate from
earlier file format versions resulting in a new config with a higher file
version.
If an existing config file does not exist, the config is populated with
the default values, however, there is no way to indicate which versions
the default values correspond to. The result is that the file version is
set to 1 for fresh configs, before the migration functions are called.
This requires the default config dict to never change, in order to be
compatible with what the migration functions expect.
A solution to this is to add a parameter to specify the file version of
the default config dict so that when a config file does not exist on disk,
the migration functions are not run because the config file format will
already be the latest version.
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2914>
Deluge <http://deluge-torrent.org/>
Deluge Project
--
You received this message because you are subscribed to the Google Groups
"Deluge Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/deluge-dev.
For more options, visit https://groups.google.com/d/optout.
