[Android Software Development] KaoDome:
Something is up with the current stable build, I installed it cleanly over an Android 13 based crDroid ROM (also clean-installed) and Google Play (store) wasn't there, despite it being supposedly installed.

The log file for that package reads the following, which seems wrong (APK installed as prop?):

----------------------------------------------------------------------------
- Working for GooglePlayStore
- package_size = 62586
- default_partition = product
----------------------------------------------------------------------------
- if product is a block, we will check if it's big enough
- fetching size for /product
- /product(/product) available size: 83232 KB
- fetched the product size to check if it's enough: 83232
- it's big enough, we'll use it
- InstallPartition is default
- InstallPartition = /product
- GooglePlayStore required size: 62586 Kb, installing to /product (product)
----------------------------------------------------------------------------
- calculating space before installing GooglePlayStore
- fetching size for /product
- /product(/product) available size: 83232 KB
- /product size left=83232
----------------------------------------------------------------------------
- Default Extn=.zip
- Install_Partition=/product
- Extn=.zip
- unpacking AppSet/Core/GooglePlayStore.zip
-> to /dev/tmp/GooglePlayStore.zip
- Unzipping /dev/tmp/GooglePlayStore.zip
-> copying installer.sh
-> to /dev/tmp/pkgContent/installer.sh
- Prop file path before:
- Prop file path after: /system/etc/permissions/GooglePlayStore.prop
----------------------------------------------------------------------------
- Installing GooglePlayStore
- Deleting Phonesky with func_result: false
- Deleted as part of package Phonesky
- Creating Directory: /product/priv-app/Phonesky
- Unzipping /dev/tmp/GooglePlayStore.zip
-> copying ___priv-app___Phonesky/Phonesky.apk
-> to /product/priv-app/Phonesky/Phonesky.apk
- File Successfully Written!
- ch_con with ___priv-app___Phonesky/Phonesky.apk for
- Creating /system/etc/permissions/GooglePlayStore.prop
- install=product/priv-app/Phonesky/Phonesky.apk >> /system/etc/permissions/GooglePlayStore.prop
- InstallPath=product/priv-app/Phonesky/Phonesky.apk
- Unzipping /dev/tmp/GooglePlayStore.zip
-> copying ___etc___permissions/com.android.vending.xml
-> to /product/etc/permissions/com.android.vending.xml
- File Successfully Written!
- ch_con with ___etc___permissions/com.android.vending.xml for
- install=product/etc/permissions/com.android.vending.xml >> /system/etc/permissions/GooglePlayStore.prop
- InstallPath=product/etc/permissions/com.android.vending.xml
- install=etc/permissions/GooglePlayStore.prop >> /system/etc/permissions/GooglePlayStore.prop
----------------------------------------------------------------------------
- calculating space after installing GooglePlayStore
- fetching size for /product
- /product(/product) available size: 22104 KB
- /product_size (22104--61128) spent=83232 vs (83232)
----------------------------------------------------------------------------

I used the full package with the config attached to this post, log archive is also attached for completeness.

EDIT:

Since I noticed /product not having much free space to begin with I chose the desired installation location instead of leaving the default, selecting /system directly. The Google Play app was present and it seems to work as expected, those logs are also attached because I could see in them mentions to /product throughout even though it actually meant /system (notably regarding the free space and where things were supposed to be installed), in case installation scripts need to be tweaked.

By the way, does the installation location matter when it comes to using the backup and restore scripts after a subsequent ROM update flash? If an app is installed that replaces their AOSP/custom ROM counterpart, like Google Clock, would it also be removed when an upgrade is done? By upgrade, let's understand flashing a new version of the ROM over a working system, they generally "unconditionally patch" it all so removed apps would be present once again.

Also, say later on I want to update to a newer NikGapps release, so that after a factory reset things are current. How would one approach it? The current installation scripts consider that a dirty install, skipping installation of packages that "can't" be installed if they weren't from the beginning, like GBoard (if I recall correctly). Perhaps it would be interesting to add a switch in the config file to force installation of those packages regardless, or them autodetecting if the problematic packages are already installed, as in installed through a clean install, allowing them to be updated to the current release.