Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flatpak on /home Option #2216

Closed
genefyx opened this issue Oct 16, 2023 · 6 comments
Closed

Flatpak on /home Option #2216

genefyx opened this issue Oct 16, 2023 · 6 comments

Comments

@genefyx
Copy link

genefyx commented Oct 16, 2023

Is your feature request related to a problem? Please describe.
I’ve defaulted to using Flatpaks, but have been running into root file size issues.
The suggested 15GB - 25GB file size resulted by search engines is no longer enough with regular Flatpak use.
In attempting to reinstall to a larger size HDD, I thought of asking for a Calamares Feature Request

Describe the solution you'd like
The option to:

Describe alternatives you've considered
I had created a Distro specific request with the option for software center.
They had suggested creating a Calamares upstream request which appears to more appropriate

Additional context
This feature would help greatly as after choosing original file sizes many users may be affected by later Flatpak usage
competing with root for file space. Thank you, I appreciate such a great installer, the "Replace a Partition" is my favorite feature and I hope this feature will be considered.

@dalto8
Copy link
Contributor

dalto8 commented Oct 16, 2023

IMO, this is something that should be distro-specific, not part of Calamares. Every distro is different.

There is an inherent assumption here that /home is larger and/or different than /. This often isn't the case.

Of course, any distro could use the functionality in Calamares to do this already using the existing modules.

Lastly, I am not sure I understand the logic of forcing system flatpaks to be installed in a single user's home directory. Flatpak already offers support for this with user flatpaks.

I had created a Distro specific request with the option for software center.

IMO, this is where it belongs. The software center should allow you to choose between system flatpaks and user flatpaks. Then there would be no need to change paths or create symlinks.

@kkofler
Copy link
Contributor

kkofler commented Oct 16, 2023

People should just stop using Flatpaks (or other containerized applications, e.g., Snaps). They are a horrible waste of space, and the bundled libraries are a security nightmare. See:

@yochananmarqos
Copy link

@dalto8

The software center should allow you to choose between system flatpaks and user flatpaks.

What software center? Neither GNOME Software, Discover nor Pamac has this feature. Why should they?

@dalto8
Copy link
Contributor

dalto8 commented Oct 18, 2023

@dalto8

The software center should allow you to choose between system flatpaks and user flatpaks.

What software center? Neither GNOME Software, Discover nor Pamac has this feature. Why should they?

flatpak provides functionality to choose if you install the flatpak to the system or for the user.

The OP is requesting a way to have flatpaks be installed to their home directory.

IMO, having the software center offer the choice between user and system installs for flatpaks much much more sense than adding functionality to Calamares to change the default flatpak location for system flatpaks to be inside the user's home directory.

Alternatively, the end-user could just configure their flatpak remotes to only have user remotes.

@adriaandegroot
Copy link
Contributor

@kkofler Stop being rude in arbitrary issues. We get it, you don't like containerized apps. That has no bearing on the technical discussion of the feature request, nor on whether it rolls out for your particular distro.

@genefyx I think the way to go for this request is to use packagechooser (which doesn't necessarily have to be about packages) to present the user with a choice -- flatpak per-user or system-wide -- and then use contextualprocess to handle that choice later. You can then do whatever configuration needs to be done in the target system, after it is installed, based on the user's choice.

This makes the feature independent: doesn't need any changes in Calamares code, and you can drop in the choice+handling into your settings.conf if it is something you like. It would be keen to have an example of the two -- eg. just the config-files and things for sertting this up -- in the calamares-extensions repo to serve as an example to other potential users.

@adriaandegroot
Copy link
Contributor

Closing as "I think this is out-of-scope" and "this has an acceptable solution without code in Calamares with existing modules".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants