6 ms·
And yet there's hundreds of apps that will never be updated or changed to conform to standards. i suspect many of those are no longer actively maintained. at b
by em-bee 6y ago
And yet there's hundreds of apps that will never be updated or changed to conform to standards.
i suspect many of those are no longer actively maintained. at best they receive security patches from distributions.
Tell that to snap. It insists its folder must sit nicely in my home folder and nowhere else.
my (low) opinion of snap aside, the bad here is that the location is not configurable. as a library of applications, i would want snap in $HOME. or i would put it in $HOME/lib or an equivalent. maybe .local would be appropriate too, but i understand it's for app specific user-data, so it doesn't look like whole apps should be in there. (edit: elsewhere i just read that .local is supposed to be like a user specific /usr/local, so snap should fit in there somewhere)
- grawprog 6y agoI don't want to turn this into a snap bad mouthing thread, but yeah. You can't even symlink it or it causes problems. It really bugs me because I don't tend to allocate too much space to my home partition and keep most of my stuff on data partitions. So if I get a bunch of snap apps, it starts eating up all the space in home.
- em-bee 6y agoi hear you. in fact, i do use data partitions as well, and if my snap directory grew to much i would want to move it too. as a workaround try to use a bind-mount
- thyrsus 6y agoCan you wrap its invocation in a script that sets a snap specific version of the $HOME environment variable? If it's perverse, it ignores $HOME in favor of reading the passwd entry itself, in which case I'm happy to have never encountered it.