MantisBT - Doomseeker
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0003452Doomseeker[All Projects] Suggestionpublic2018-08-20 21:272023-02-19 14:12
ReporterWubTheCaptain 
Assigned ToZalewa 
PrioritynoneSeverityfeatureReproducibilityN/A
StatusresolvedResolutionfixed 
Platformx86_64OSDebian GNU/LinuxOS Versionbuster/sid
Product Version1.1 
Target Version1.4.0Fixed in Version1.4.0 
Summary0003452: Add an option to select a Doomseeker environment path on startup
DescriptionIt griefs me a little to copy & move config directories (and other Doomseeker directories) around on the file system when trying to debug issues, such as 0003411 or maybe even 0003396.

If there was a command line option (such as --configdir) or an environment variable to manipulate the directory Doomseeker looks for its config (doomseeker.ini) and possibly .cache & .local/share, it'd make my life a bit easier. :)
Steps To ReproduceFrom the command line, pass the --help flag to Doomseeker executable:

$ doomseeker --help


Notice there's no option available for the described suggestion.
Additional Information
TagsNo tags attached.
Relationships
related to 0000049feedback  Doomseeker - Allow multiple masters 
related to 0004081resolved Zalewa Doomseeker 1.1 config migration getting in the way of --basedir 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2018-08-20 21:27WubTheCaptainNew Issue
2018-08-20 21:28WubTheCaptainSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=11632#r11632
2018-08-20 21:37WubTheCaptainSummaryAdd a command line option to select config directory path => Add an option to select a Doomseeker environment path on startup
2018-08-20 21:41WubTheCaptainNote Added: 0019356
2018-08-21 23:36Blzut3Note Added: 0019381
2018-08-24 01:53WubTheCaptainStatusnew => acknowledged
2018-08-24 01:54WubTheCaptainPrioritynormal => low
2019-04-19 18:34WubTheCaptainPrioritylow => none
2019-04-19 18:53WubTheCaptainRelationship addedrelated to 0000049
2022-12-17 23:37ZalewaTarget Version => 1.4.0
2022-12-18 14:22ZalewaAssigned To => Zalewa
2022-12-18 14:22ZalewaStatusacknowledged => assigned
2022-12-24 21:19ZalewaNote Added: 0022563
2022-12-24 21:19ZalewaStatusassigned => needs review
2023-01-02 10:07ZalewaRelationship addedrelated to 0004081
2023-01-05 12:25ZalewaNote Added: 0022657
2023-01-05 12:25ZalewaStatusneeds review => needs testing
2023-02-19 14:12ZalewaStatusneeds testing => resolved
2023-02-19 14:12ZalewaFixed in Version => 1.4.0
2023-02-19 14:12ZalewaResolutionopen => fixed

Notes
(0019356)
WubTheCaptain   
2018-08-20 21:41   
If anyone has a better solution that doesn't require adding more features to Doomseeker, I'm all up for it. But there's already a --datadir option for IP2C data and plugins, mind you.
(0019381)
Blzut3   
2018-08-21 23:36   
While not exactly what you're looking for --portable could work with some limitations.
(0022563)
Zalewa   
2022-12-24 21:19   
I have added a --basedir argument for that. I chose not to use --configdir because the "config" dir is only one of the directories that the Doomseeker uses. The other 2 are the cache and the managed files. --basedir configures the prefix path for all 3 of them.

'https://bitbucket.org/Doomseeker/doomseeker/commits/d47e2cfba63fb5e83d9e79170832d2e5e66dab73 [^]'

Now `--basedir <path/to/doomseeker.exe/dir>` and `--portable` do nearly the same aside from suggesting the user a different directory to save the unmanaged files: "My Documents" in non-portable mode, and the exe dir in the portable mode. Despite the functional similarity, `--portable` should not be removed for compatibility reasons and because `--portable` describes a different intent than `--basedir`.
(0022657)
Zalewa   
2023-01-05 12:25   
Beta package for Windows available at the beta auto-update channel and at:
'https://devbuilds.drdteam.org/doomseeker/doomseeker-1.3.3~beta-230105-1140_windows.zip [^]'

Please test `--basedir <somewhere>` and also in a combination `--portable --basedir <somewhere>`.