[GH-ISSUE #31] Use XDG spec directories #22

Closed
opened 2026-05-05 04:47:10 -06:00 by gitea-mirror · 5 comments
Owner

Originally created by @AdrianKoshka on GitHub (Apr 26, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/31

Using the XDG specification directories would not only make the linux package work better as a flatpak, but play nicer with distributions in general. This was mentioned in #30.

  • XDG_CONFIG_HOME
  • XDG_DATA_HOME
  • XDG_CACHE_HOME

flatpak specific docs
XDG Base Directory spec as documented by FreeeDesktop

Originally created by @AdrianKoshka on GitHub (Apr 26, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/31 Using the `XDG` specification directories would not only make the linux package work better as a flatpak, but play nicer with distributions in general. This was mentioned in #30. - `XDG_CONFIG_HOME` - `XDG_DATA_HOME` - `XDG_CACHE_HOME` flatpak specific [docs](http://docs.flatpak.org/en/latest/conventions.html#xdg-base-directories) [XDG Base Directory spec as documented by FreeeDesktop](https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html)
gitea-mirror 2026-05-05 04:47:10 -06:00
Author
Owner

@walker0643 commented on GitHub (May 7, 2018):

@AdrianKoshka if i missed anything with the patch let me know. thanks for the suggestion!

<!-- gh-comment-id:387140447 --> @walker0643 commented on GitHub (May 7, 2018): @AdrianKoshka if i missed anything with the patch let me know. thanks for the suggestion!
Author
Owner

@AdrianKoshka commented on GitHub (May 7, 2018):

Looks good, haven't tested. Did you make a new release? Flathub doesn't allow just pointing to master if the source is a git repo.

<!-- gh-comment-id:387164169 --> @AdrianKoshka commented on GitHub (May 7, 2018): Looks good, haven't tested. Did you make a new release? Flathub doesn't allow just pointing to master if the source is a git repo.
Author
Owner

@walker0643 commented on GitHub (May 7, 2018):

Nope. Tagging will happen once I hear from the various package maintainers that they do not need any additional code changes in order to proceed.

<!-- gh-comment-id:387183402 --> @walker0643 commented on GitHub (May 7, 2018): Nope. Tagging will happen once I hear from the various package maintainers that they do not need any additional code changes in order to proceed.
Author
Owner

@AdrianKoshka commented on GitHub (May 7, 2018):

Alright, I'll keep an eye out then for whenever the next tag is out.

<!-- gh-comment-id:387187413 --> @AdrianKoshka commented on GitHub (May 7, 2018): Alright, I'll keep an eye out then for whenever the next tag is out.
Author
Owner

@walker0643 commented on GitHub (May 14, 2018):

2.1 tagged

<!-- gh-comment-id:388903129 --> @walker0643 commented on GitHub (May 14, 2018): 2.1 tagged
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#22
No description provided.