[Enhancement] Directories and files should be in accordance with XDG base directory spec #157
Labels
No Label
bug
build
dependencies
developers
documentation
duplicate
enhancement
formatting
invalid
legal
mobile
obsolete
packaging
performance
protocol
question
refactoring
regression
security
test
translation
usability
wontfix
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Bitmessage/PyBitmessage-2024-12-12#157
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
On Linux, Pybitmessage uses
~/.PyBitmessage
. Instead, it should respect the XDG Base Directory Specification, which means~/.config/pybitmessage
($XDG_CONFIG_HOME) for keys.dat and so on.I agree, I'll put that on my TODO list.
Reasons, expressed better than I could.
(I'll put in a pull request when I implement migration.)
Sorry about the mess, I forgot to base my changes off of
Bitmessage/PyBitmessage master
Please close this issue.
xj9, thank you very much for your patch. 👍
I think this bug report should stay open until every file has its right place according to the XDG standard:
$XDG_CONFIG_HOME/pybitmessage
: keys.dat$XDG_CACHE_HOME/pybitmessage
: debug.log and knownnodes.dat$XDG_DATA_HOME/pybitmessage
: messages.datHasn't this been fixed already?
Ok, so now it puts everything into XDG_CONFIG_HOME, if the variable exists. While I understand what the standard wants to achieve, I am not sure it's a good fit for PyBitmessage, since the directory structure would differ from portable mode. It needs to be investigated.
I agree with my previous post, solitting this into 3 directories doesn't fit into the design of PyBitmessage.