As of task-2.6 XDG directories are fully supported but the most recent ebuild does not reflect this. Per the the upstream documentation: in order for that to work out of the box the taskrc file must be relocated to $XDG_CONFIG_HOME/task/taskrc. Also the following lines need to be uncommented in the default taskrc file: #data.location=~/.local/share/task #hooks.location=~/.config/task/hooks I did some testing and it appears that any existing ~/.taskrc takes precedence over one present in ~/.config/task/taskrc, so existing task lists shouldn't appear to go missing after upgrading to an ebuild with this change. But you might want to add an einfo just in case.
(In reply to Jeff Gazso from comment #0) > As of task-2.6 XDG directories are fully supported but the most recent > ebuild does not reflect this. Per the the upstream documentation: in order > for that to work out of the box the taskrc file must be relocated to > $XDG_CONFIG_HOME/task/taskrc. > > Also the following lines need to be uncommented in the default taskrc file: > > #data.location=~/.local/share/task > #hooks.location=~/.config/task/hooks > But that's not respecting XDG_* variables, it's just picking new (assumed) locations. > I did some testing and it appears that any existing ~/.taskrc takes > precedence over one present in ~/.config/task/taskrc, so existing task lists > shouldn't appear to go missing after upgrading to an ebuild with this > change. But you might want to add an einfo just in case. That part is good though.
Sorry for the delay. I'm looking at this now. I guess supporting does not mean that existing installs *should* respect that (see https://github.com/GothenburgBitFactory/taskwarrior/issues/438). The way to make the transition from the default configuration to the XDG compliant one is well documented in taskrc and looks like it works out of the box: I'll add an einfo so that XDG users know that it is possible. In the future please link upstream documentation when you refer to it.
