PathPicker pollutes user home directory about pathpicker

[SamHasler]

Would supporting XDG_CONFIG_HOME if it's set give more users a cleaner home
dir by default?
On Dec 30, 2015 5:23 PM, "Peter Cottle" [email protected] wrote:

Yeah I would be fine with that -- would accept the PR as long as it has a
sane default and some basic test coverage (and would be in the help
output). We have a number of env variables right now but so far its
manageable

—
Reply to this email directly or view it on GitHub
#17 (comment).

[pcottle]

Yeah I have been meaning to get around to this -- totally can as well. a few questions for you @vitaut:

• is the current user always guaranteed to have write capabilities into $HOME/.local/share? one of the nice things about the home directory is not having to worry about user permissions
• is it guaranteed to exist? or will we have to mkdir -p beforehand?

I'd love to resolve this though, and it shouldnt be hard since these are all constants in the code

[vitaut]

Although all systems I've been working on have writable $HOME/.local/share, I can't say whether this directory is guaranteed to exist, so it's probably safer to check and create if it doesn't.

On a closer inspection though.fbPager* files look more like temporary files (are they?) rather than some user-specific settings and could probably be stored in /tmp.

[pcottle]

yeah they are all temporary -- the only one that persists between sessions is the selection pickle and if thats gone its nbd.

same question -- is /tmp always guaranteed to be writeable? or on average more guaranteed to be writeable and exist compared to a home dir?

[vitaut]

I think it's safe to assume that /tmp is writable.

[pcottle]

Alright -- this is coming tomorrow!

we'll be sharing the same pickle selection across users on the same machine, so maybe we should prepend by the username? pwd.getpwuid(os.getuid()).pw_name

[zkanda]

I think it's safe to assume that everything under the users directory is owned by the user.

A lot of projects is either using $HOME/.config or a dedicated folder in home:
E.g.

[lastquestion]

$HOME/.fpp is preferable to me... that way fpp doesn't have to deal with user issues.
proposed PR: #77

[pcottle]

Fixed by #77 !

[mcchrish]

Should it be possible to define a custom FPP_DIR environment variable? Say, I want to move it to $HOME/.config/fpp.

[pcottle]

Yeah I would be fine with that -- would accept the PR as long as it has a sane default and some basic test coverage (and would be in the help output). We have a number of env variables right now but so far its manageable

[vitaut]

👍 for $HOME/.config/fpp. Adding another, even hidden, directory in $HOME just for one application looks like an overkill.

[vitaut]

@SamHasler XDG_CONFIG_HOME may not be set by default (it is not set on Ubuntu 14.04 for instance).

[SamHasler]

I know. I'm just saying if XDG_CONFIG_HOME is set, use it, as that's where
that user keeps their config.
On Dec 31, 2015 2:25 PM, "Victor Zverovich" [email protected]
wrote:

@SamHasler https://github.com/SamHasler XDG_CONFIG_HOME may not be set
by default (it is not set on Ubuntu 14.04 for instance).

—
Reply to this email directly or view it on GitHub
#17 (comment).