Proton enables packages that should be disabled about proton

[sglyon]

Ahh I just noticed this the other day and was going to open an issue once I investigated more to find the issue.

Any thoughts on how to resolve?

[dvcrn]

1. We could blatantly enable everything before layer-init, but that would result that some of the needed packages are not there yet because the packages list could change after init.
2. Layers could keep track if a package is disabled / enabled and remove it from get-packages
3. We tweak enable/disable to save the package state and filter all disabled-packages (by proton) with all packages that layers need
4. We provide a separate API that layers can use to disable / enable a package. Something like mark-enabled and mark-disabled. Core is then only enabling packages that are marked as enabled.

Just some thoughts

[geksilla]

I like 4.

We provide a separate API that layers can use to disable / enable a package. Something like mark-enabled and mark-disabled. Core is then only enabling packages that are marked as enabled.

[geksilla]

@dvcrn, I made experimental branch feel free to check it out.

[dvcrn]

@geksilla very nice. I'll see if I can use this!

[dvcrn]

Your change seem to have mostly fixed this. I am closing this issue.