American_Jesus@lemm.ee to Linux@lemmy.ml · 1 year agoDotfiles matter! Please stop dumping files in users’ $HOME directories.dotfiles-matter.clickexternal-linkmessage-square152fedilinkarrow-up1685arrow-down19cross-posted to: programming@programming.dev
arrow-up1676arrow-down1external-linkDotfiles matter! Please stop dumping files in users’ $HOME directories.dotfiles-matter.clickAmerican_Jesus@lemm.ee to Linux@lemmy.ml · 1 year agomessage-square152fedilinkcross-posted to: programming@programming.dev
minus-squarenous@programming.devlinkfedilinkEnglisharrow-up34arrow-down1·1 year agoThe software can read from both locations in a backwards compatible way. Many tools already do this.
minus-squareCosmicTurtle@lemmy.worldlinkfedilinkEnglisharrow-up7arrow-down4·1 year agoThe best way to handle this is to have the next version move the old directory (if it exists) and then start reading from there. That way it’s in compliance from then forward. A UI notice is nice but will probably be ignored.
minus-squaredonnachaidh@lemmy.dcmrobertson.comlinkfedilinkarrow-up3·1 year agoThat could break some peoples’ dotfile management, e.g. symlinks or git repos. I’d say deprecation notice and reading from both, at least for a while, is better.
The software can read from both locations in a backwards compatible way. Many tools already do this.
The best way to handle this is to have the next version move the old directory (if it exists) and then start reading from there.
That way it’s in compliance from then forward.
A UI notice is nice but will probably be ignored.
That could break some peoples’ dotfile management, e.g. symlinks or git repos. I’d say deprecation notice and reading from both, at least for a while, is better.