| Home | Trees | Indices | Help |
|
|---|
|
|
| Instance Methods | |||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
| string or None |
|
||
| tuple(set, bool) |
|
||
| set |
|
||
| Method Details |
Returns path of the branch migration status file.
This file is placed inside the Entropy client directory to determine
if post-branch migration script has been run.
The content of this status file is usually something like this:
"<mtime> => <from branch> => <to branch>
"
@param repoid: repository identifier
@type repoid: string
@return: branch migration status file path or None
@rtype: string or None
|
Returns path of the branch upgrade status file. This file is placed inside the Entropy client directory to determine whether running post-upgrade ("equo upgrade") repository branch update scripts. This file contains no data.
|
This method is called whenever branch is successfully switched by user. Branch is switched when user wants to upgrade the OS to a new major release. Any repository can be shipped with a sh script which if available, handles system configuration to ease the migration.
|
This method is called whenever branch is successfully switched by user and all the updates have been installed (also look at: run_repositories_post_branch_switch_hooks()). Any repository can be shipped with a sh script which if available, handles system configuration to ease the migration.
|
| Home | Trees | Indices | Help |
|
|---|
| Generated by Epydoc 3.0.1 on Sun Jun 28 00:23:23 2009 | http://epydoc.sourceforge.net |