Here are some thoughts I had to fix this. It is not fully realized:
We take advantage of tunables in the following manner:
* create tunables/xdg to have:
@{XDG_DESKTOP_DIR}=@{HOMEDIRS}/*/Desktop
#include <tunables/xdg.d>
* tunables/xdg.d could include files with contents of the form:
@{XDG_DESKTOP_DIR}+=@{HOMEDIRS}/*/TranslatedDesktop
* we could then have some sort of a hook, perhaps a dpkg trigger that would generate files in tunables/xdg.d based on installed locales
Rules that were of the form of:
owner @{HOME}/Desktop/** r,
would become:
owner @{XDG_DESKTOP_DIR/** r,
This also has the advantage of opening the possibility of handling migrations like those with /var/run/user/ to be handled more gracefully.
Here are some thoughts I had to fix this. It is not fully realized:
We take advantage of tunables in the following manner: DESKTOP_ DIR}=@{ HOMEDIRS} /*/Desktop DESKTOP_ DIR}+=@ {HOMEDIRS} /*/TranslatedDe sktop
* create tunables/xdg to have:
@{XDG_
#include <tunables/xdg.d>
* tunables/xdg.d could include files with contents of the form:
@{XDG_
* we could then have some sort of a hook, perhaps a dpkg trigger that would generate files in tunables/xdg.d based on installed locales
Rules that were of the form of:
owner @{HOME}/Desktop/** r,
would become: DIR/** r,
owner @{XDG_DESKTOP_
This also has the advantage of opening the possibility of handling migrations like those with /var/run/user/ to be handled more gracefully.