Opened 4 years ago

Closed 3 years ago

#14086 closed defect (fixed)

Restructure directories where ooni software writes/reads from

Reported by: hellais Owned by: hellais
Priority: Medium Milestone:
Component: Archived/Ooni Version:
Severity: Normal Keywords:
Cc: weasel, lunar Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by hellais)

Currently the data that ships with ooniprobe will be written to either /usr/share/ooni or /path/to/virtualenv/share/ooni if it was installed in a virtualenv. This data however also needs to be periodically updated via the ooniresources command line tool

It has been suggested by @Lunar and @weasel that these are not the best locations for files that need to be updated/written by binaries.
For this reason it has been suggested to write system wide files that require updating to /var/lib/ooni or ~/.ooni/.
The tools that require such files should first search inside of ~/.ooni, then /var/lib/ooni, finally in /usr/share/ooni. If no files are found in any of these directories it should then prompt to run the ooniresources script to fetch the files.

Child Tickets

Change History (3)

comment:1 Changed 4 years ago by hellais

Description: modified (diff)

comment:2 Changed 4 years ago by hellais

Status: newneeds_revision

A pull request implementing this has been issued: https://github.com/TheTorProject/ooni-probe/pull/372

comment:3 Changed 3 years ago by anadahz

Resolution: fixed
Severity: Normal
Status: needs_revisionclosed

Assuming that is fixed since pull request has been merged.
Please reopen if this not the case.

Note: See TracTickets for help on using tickets.