[v3alpha]: pmboostrap does not use the entered work-dir
tested pmboostrap from the latest master (commit 2ce06e97) and noticed the following behavior when running the pmbootstrap init as recommeneded after the switch from 2.3.1 to 3_0_0_alpha:
$ pmbootstrap init
[20:00:08] Location of the 'work' path. Multiple chroots (native, device arch, device rootfs) will be created in there.
[20:00:08] Work path [/pmb]: /pmb
[20:00:12] Setting up the native chroot and cloning the package build recipes (pmaports)...
[20:00:12] Clone git repository: https://gitlab.com/postmarketOS/pmaports.git
Cloning into '/home/robby/.local/var/pmbootstrap/cache_git/pmaports'...
Updating files: 100% (6246/6246), done.
[20:00:28] Choose the postmarketOS release channel.
After completing the init
running pmbootstrap config
gives the following:
$ pmbootstrap config
[pmbootstrap]
aports = /home/robby/.local/var/pmbootstrap/cache_git/pmaports
...
user = rob
work = /pmb
[providers]
[mirrors]
...
Shouldnt the aports be located below the work-dir?
Or was this changed in the past and I am now hitting an edge-case?