

I’m a bit confused.
The idea is to contain all non-FOSS apps in a workspace. I assume that I’ll have trouble without microg for some apps in said workspace, which is why I’m looking for a way to put microG in that workspace.
The rest of the apps will all be FOSS. Thus, I do not see a good reason to bundle MicroG in the base image. I’d like to keep all non-FOSS+Google stuff in one workspace and not have them touch the rest of my apps.
I’m assuming workspaces are akin to a “namespace” in general Linux terminology.
The problem you are going to run into though is that google has baked itself into android that you need something to trick android into thinking its operable.
In stock android, you COULD have a workspace that only uses microg, but considering you otherwise MUST have play services… Why?
What do you mean? I genuinely do not understand, I thought DeGoogled AOSP would work just fine.
I think we are still miscommunicating, partly due to my fault.
When I said “workspaces” what I meant is a “Work Profile” - you know, the kind of thing you manage with the shelter app and that companies use MDM for to manage their company-specific apps.
Android doesn’t make these decisions, Google does. It is a common misconception that Google ships AOSP with Pixel. They do not.
If you don’t want Google apps, either install a custom ROM or get root access (I hear KernelSU is making great progress). I don’t think your point is valid, you’re talking about stock ROMs. I’m not. And God help people who buy from a carrier, that’s probably the worst way to get a mobile phone.
Don’t want to use PlayStore? Use Accrescent + Obtanium + F-Droid + Aurora (preferably in that order). There is no longer a reason to have playstore installed on your device unless one of these FOSS projects die or you paid for apps from the playstore before. I’m perfectly comfortable with using these instead of the pre installed spyware they ship me.
AOSP is not a workaround, it’s what Google bases their OS on (what they ship with the Pixel) along with other manufacturers. Yes, Google writes a lot of AOSP but it is FOSS and available to anyone. Otherwise Huawei wouldn’t be able to make Android devices at all.
eOS is FOSS. Murena is the business. And no, I don’t agree - they could have at least given us an option (like LineageOS does) to either have microG or not have it in the base image. This is not a hard thing to do.
I suppose I can just rip MicroG out and only install it in a “Work Profile” but not having to do that would be a great QoL upgrade.
Giving credit where it is due: due to Google’s efforts in making project Treble compatibility mandatory along with further enhancements to the Android software ecosystem, you can technically run AOSP’s (or really, any ROM’s) GSI on any phone you can unlock the bootloader to. That is only possible on the Pixels, older OnePluses, some Motorolas and some Nothing Phones in the US, excluding Murena’s phones and some other niche manufacturers. There are caveats due to proprietary firmware but that’s where we are right now.
In conclusion: I would have liked an eOS without MicroG pre-installed. I suppose I could rip it out but I’m afraid I’ll miss some artifacts. But that’s a minor worry. I’m sorry for the long note.
How authors of software projects behave has never been my concern when evaluating their projects technically. I’m no expert, but I’ll pay tribute to Gr******OS for everything that they have done for the community; hardened Malloc by itself is a great advancement in the Linux kernel. Unfortunate that two people like them at the forefront of FOSS have disagreements, but I do not care. I hope both of them live long and healthy and bring FOSS even greater achievements.