Is your feature request related to a problem? Please describe.
In LineageOS, and other distributions relying on lineageos4microg project to include microG, we are having issues with using a /system-based path to find the microg.xml in builds that are marked as strict which doesn't let system partition to have much additions, see lineageos4microg/android_vendor_partner_gms#44
However, in microG, putting a /system/etc/microg.xml is the only way to provide build-time default settings.
Describe the solution you'd like
Another path such as /product/etc/microg.xml can be added such that microG checks that first and if it doesn't exist, then fall back to /system/etc/microg.xml so that no existing builds break and we can switch to /product/etc/microg.xml in future builds.
Describe alternatives you've considered
We tried to add it as exception but it doesn't work in strict builds lineageos4microg/android_vendor_partner_gms#46
Is your feature request related to a problem? Please describe.
In LineageOS, and other distributions relying on
lineageos4microgproject to include microG, we are having issues with using a/system-based path to find themicrog.xmlin builds that are marked as strict which doesn't let system partition to have much additions, see lineageos4microg/android_vendor_partner_gms#44However, in microG, putting a
/system/etc/microg.xmlis the only way to provide build-time default settings.Describe the solution you'd like
Another path such as
/product/etc/microg.xmlcan be added such that microG checks that first and if it doesn't exist, then fall back to/system/etc/microg.xmlso that no existing builds break and we can switch to/product/etc/microg.xmlin future builds.Describe alternatives you've considered
We tried to add it as exception but it doesn't work in strict builds lineageos4microg/android_vendor_partner_gms#46