Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
have something uniform
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
'sisyphus upgrade --hybrid')
|
|
|
|
repository/branch compatibility once the switch is completed
|
|
|
|
branchnext modules; plug the new module into the new cli client -> works magic
|
|
update, upgrade, rescue, spmsync, autoremove - all work
|
|
|
|
module -> mirror setup works
|
|
|
|
|
|
|
|
|
|
|
|
under one module, and expose them to other modules from there
|
|
|
|
errors
|
|
to work with the new backend ... gui frontend wip
|
|
|
|
clue of what is happening
|
|
rebuilds
|
|
|
|
|
|
* git reset --hard is a bit overkill for portage config files sync
as it will reset MAKEOPTS, custom USE flags, keywords, masks etc
* to preserve them, use git stash right before the hard reset, and
then apply the stash
|
|
|
|
|
|
some functions
|
|
a bit to make it more reliable
|