Bitmessage/PyBitmessage-2025-02-23
Archived
2
0
Fork 0
Code Issues 167 Pull Requests 54 Actions Packages Projects Releases 5 Wiki Activity

[Enhancement] Directories and files should be in accordance with XDG base directory spec #157

New Issue
Closed
opened 2013-05-17 12:09:04 +02:00 by omyno · 8 comments
omyno commented 2013-05-17 12:09:04 +02:00 (Migrated from github.com)
Copy Link

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.

On Linux, Pybitmessage uses `~/.PyBitmessage`. Instead, it should respect the [XDG Base Directory Specification](http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html), which means `~/.config/pybitmessage` ($XDG_CONFIG_HOME) for keys.dat and so on.
r14c commented 2013-06-23 01:18:44 +02:00 (Migrated from github.com)
Copy Link

I agree, I'll put that on my TODO list.

I agree, I'll put that on my TODO list.
r14c commented 2013-06-26 10:19:03 +02:00 (Migrated from github.com)
Copy Link

Reasons, expressed better than I could.

(I'll put in a pull request when I implement migration.)

[Rea](http://stick.gk2.sk/2009/03/the-ugly-duckling-called-xdg_config_home/)[son](http://unix.stackexchange.com/a/38871)s, expressed better than I could. (I'll put in a pull request when I implement migration.)
r14c commented 2013-06-26 11:25:17 +02:00 (Migrated from github.com)
Copy Link

Sorry about the mess, I forgot to base my changes off of Bitmessage/PyBitmessage master

Sorry about the mess, I forgot to base my changes off of `Bitmessage/PyBitmessage master`
nimdahk commented 2013-08-13 00:55:51 +02:00 (Migrated from github.com)
Copy Link

Please close this issue.

Please close this issue.
omyno commented 2013-08-14 02:26:14 +02:00 (Migrated from github.com)
Copy Link

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.dat
xj9, thank you very much for your patch. :+1: I think this bug report should stay open until every file has its [right place](http://ploum.net/207-modify-your-application-to-use-xdg-folders/) 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.dat
PeterSurda commented 2017-02-22 18:17:47 +01:00 (Migrated from github.com)
Copy Link

Hasn't this been fixed already?

Hasn't this been fixed already?
PeterSurda commented 2017-02-26 12:25:11 +01:00 (Migrated from github.com)
Copy Link

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.

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.
PeterSurda commented 2020-09-30 11:55:20 +02:00 (Migrated from github.com)
Copy Link

I agree with my previous post, solitting this into 3 directories doesn't fit into the design of PyBitmessage.

I agree with my previous post, solitting this into 3 directories doesn't fit into the design of PyBitmessage.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working as it's supposed to
build
Related to building or build system
dependencies
Pull requests that update a dependency file
developers
The issue is relevant mainly for developers rather than users
documentation
duplicate
enhancement
New feature
formatting
Code or UI text formatting
invalid
legal
mobile
Frontend for mobile devices (kivy)
obsolete
packaging
performance
protocol
Protocol change
question
refactoring
regression
Some issue, fixed in the past, appears again
security
test
translation
usability
wontfix
No Label
bug
Milestone
No items
No Milestone v0.6.4
Projects
Clear projects
No project
Assignees
Clear assignees
PeterSurda
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2025-02-23#157
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?