Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
'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
|
|
* backend :
* make sync more reliable and future proof (in case we will have more branches)
* while the bugfix commit 12c2d64d475552f7ccfb078613a8fbfcea1efaba fixed a long stading bug
* it also slowed us down considerably triggering metadata refresh when it wasn't actually
* needed. Rework the code to trigger metadata refresh only when absolutely needed
* this will speed up things considerably, specially dependency resolution
|
|
This reverts commit 9dbe22f88fae49eac34bdb123f2e1acfc24a6a99.
|
|
|
|
|
|
|
|
* since our sync method is different than portage, sisyphus may fail to resolve dependencies properly in certain cases
* copy portage's behaviour, perform global updates (SLOT moves, blockers etc) and refresh the metadata after every sync
* while this will slow down the sync a little, it will accelerate dependency solving considerably
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
options to use gitlab.com or pagure.io as remote
|
|
exact same name but they aZre in different categories (e.g.: acct-group/mail-0.tbz2 && acct-user/mail-0.tbz2)
|
|
|