Remove flatpak apps installed via flatpak preinstall - #163
Conversation
|
I'd like to go ahead and merge this because it's blocking mkosi images. It sounds like it's possible we can also build non-atomic builds with mkosi, so we might not need the default settings branch either way |
I personally think we may want to use the default-settings to keep the preinstall conf file instead of relying on mkosi, at least for now. It's not yet decided that we switch from live-build to mkosi on OS 9, so I'm concerning that premising mkosi at this time could be a risk if mkosi image were to be postponed for further major releases. And if mkosi image is surely land on OS 9 then we can revisit if the preinstall conf file should be the os repository instead of default-settings. What do you think? |
|
@ryonakano I think maybe it would be better to put it in the OS repo for livebuild so that we're not breaking/blocking mkosi builds? Or I'm not sure if we can put it in default settings for both? @jumpyvi any thoughts? |
|
@jumpyvi I'm still not familiar with mkosk so I'm not sure whether we should have separated preinstall files for live-build and mkosk branches (probably results the same content), or we can just put it in the default-settings repository. What do you think? |
|
Looks like you created a dedicated systemd service in the mkosi branch, so probably we should maintain in the default-settings repository so as not to have duplicated works? |
Yes, I think it would be fine default-settings. But yeah, include the systemd script. |
|
@jumpyvi I imported your systemd service file into default-settings in the following PRs: |
Should this be included package-side too? |
|
Hmm it worked for me without it 🤔 |
There might be some other package that provides the repo. |
|
@jumpyvi OK, I think we don't need to provide Latest branch of default-settings just installs the Footnotes
|
Part of elementary/os#783
Goes after elementary/default-settings#364