fix pmbootstrap's confusion between aports and pmaports

In some places, when pmbootstrap refers to pmaports, it actually says "aports". pmbootstrap's config key is aports, for example. It would be nice to fix this.

mentioned in issue #1907

By Antoine Fontaine on 2020-04-14T23:57:09

added complex help wanted labels

added consistency label

The reasoning is explained in the wiki:

pmaports stands for postmarketOS aports, and aports in turn are the Alpine ports. The name pmaports was chosen when pmaports.git was split from pmbootstrap.git in 2018 (#383 (closed)), to make obvious that this is not a fork of Alpine's aports.git repository. Before that, it was a subdirectory called aports in the pmbootstrap.git repository. Therefore pmbootstrap sometimes refers to pmaports as "aports" (e.g. pmbootstrap config aports and pmbootstrap --aports are both about pmaports, not Alpine's aports).

I agree that it would be nice to have "aports" always refer to the Alpine ports, and never to the pmaports.

Regarding the pmbootstrap.cfgt config option, we could change it to "pmaports" and add some backwards compatibility code for "aports".

To have it properly in all places is probably a complex task, so I'll mark it as such.

By Oliver Smith on 2020-04-19T16:25:30

changed milestone to %3.0.0 critical path (blockers only!!)

I think it would be good to address this before pmbootstrap 3.0.0 is out. At least changing the --aports argument to --pmaports, and renaming the resulting .aports in the code to .pmaports.

By Oliver Smith on 2024-07-01T20:34:37

removed complex label

mentioned in merge request !2342 (merged)

By Oliver Smith on 2024-07-01T20:37:38

Trying to get 3.0.0 out of the door, so unassigning this issue form the milestone.

At least changing the --aports argument to --pmaports, and renaming the resulting .aports in the code to .pmaports.

Maybe this / part of this could be done as part of #2412 (closed) which is a blocker for v3.

removed milestone %3.0.0 critical path (blockers only!!)