Administration/pmbootstrap-meow
2
0
Fork 0
forked from Mirror/pmbootstrap
Code Pull requests Activity Actions

Use pmbootstrap_v3.cfg as config file (MR 2350)

Browse source 
Using pmbootstrap v3 with the old config can cause problems, for example
when having $WORK in the pmaports dir instead of the actual work path.
This is not supported anymore by v3 to reduce complexity. The format of
how mirrors are stored in the config also has changed.

Use a separate config file, so users can go back from v3 to 2.3.x if
they need to (for figuring out a regression) and so users won't run into
bugs when moving from 2.3.x to v3.
This commit is contained in:
Oliver Smith 2024-07-07 20:48:57 +02:00 • committed by Caleb Connolly
parent 3d9607aa99
commit 9dfa89c58c
No known key found for this signature in database
GPG key ID: 0583312B195F64B6
11 changed files with 15 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

4
pmb/config/init.py
View file

@ -135,8 +135,8 @@ def ask_for_channel(config: Config):
# Default for first run: "recommended" from channels.cfg
# Otherwise, if valid: channel from pmaports.cfg of current branch
# The actual channel name is not saved in pmbootstrap.cfg, because then we
# would need to sync it with what is checked out in pmaports.git.
# The actual channel name is not saved in pmbootstrap_v3.cfg, because then
# we would need to sync it with what is checked out in pmaports.git.
default = pmb.config.pmaports.read_config()["channel"]
choices = channels_cfg["channels"].keys()
if config.is_default_channel or default not in choices: