Skip to content

"Is Flatpak tied to systemd" could probably use an update once that question is settled (is it?) #729

@ell1e

Description

@ell1e

"Is Flatpak tied to systemd" https://flatpak.org/faq/#Is_Flatpak_tied_to_systemd_ could probably use an update once that question is settled for future flatpak versions (and I don't know if that's the case or not, I've just heard various news places mention that this seems to be changing).

I'm personally interested what the answer is as an end-user, simply wanting to plan whether I should continue to rely on Flatpak or start looking for different workflows. Typically it takes me a while to fully leave behind a previous solution so I like to start switching early.

(Why I'm watching it closely: even KDE with the elogind replacement is no longer being actively officially supported by my non-systemd distribution since apparently it's not easy enough to package without systemd. So I imagine if there is any effort at all to getting a future flatpak technology to run without systemd, then I'm kinda expecting that it may no longer be available on my system in the future. However, this is just a super uninformed guess coming from previous end user experience.)

Please note I'm by no means saying you shouldn't rely on systemd.

I'm just trying to neutrally suggest you should update that question if the info is available, or once it is available, and I'm giving an example why people may want to know and what details might matter to them for this question.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions