+39
Declined

Add command line option to alter replace root path

Shawn 3 years ago • updated by Canneverbe Limited 6 months ago 9

One of the things that makes Ketarin less portable than it could be is that the complete download path is preserved in the data structure. If I use a USB stick as my local cache and more it to another device, if I don't match up the drive letter, a bunch of files might be re-downloaded or treated as missing.


One way around this is to find/replace the old path with the new path in an export/import operation, but it would be better if the paths were either not rooted (only partial paths) or if there were a way to replace the root path via the command line.


An example of the export code that demonstrates the problem is here:

...
<SourceType>FixedUrl</SourceType>
<PreviousLocation>K:\_Ketarin\Ketarin\..\Security\CertData-11 Oct 2016.txt</PreviousLocation>
<DeletePreviousFile>true</DeletePreviousFile>
...
<LastUpdated>2016-10-11T11:17:43.7694214-07:00</LastUpdated>
<TargetPath>..\{category}\{appname:regexreplace:([\s\t\r\n\-\\&\/]+):_}-{version}.{url:ext}</TargetPath>
<FixedDownloadUrl>{dl}</FixedDownloadUrl>
...


If I plug this drive into another computer that doesn't reflect it as "K:" I have to change the drive letter before I can have Ketarin run consistently.

Answer

Answer
Declined

I'll close this for now since I do not see a issue here currently. If a specific problem occurs, I will fix it though (please post in the forum) since there shouldn't be any portability issues with Ketarin.

When you request features, you should give it a vote though. At least one ;)

Isn't this already implemented?

No. The PreviousLocation is preserved as a complete path and only the file that exists at that path is compared with the previous version, if it's missing or that path doesn't exist it redownloads it even if the constructed path (including variables) exists.

Under review

Why isn't the variable "root" helping in this case? Also Ketarin stores the relative path as well and uses it as a "backup". What are the exact problems with portable usage?

Checking for updates with a different drive letter always re-downloads the same files. I don't use "root", though, just ".." to get to the folder above where Ketarin is installed. I don't want downloads at the root of the drive, but stored relative to where Ketarin is located (usually store files in "K:\_Ketarin" or "?:\Support" with Ketarin installed in "K:\_Ketarin\Ketarin" or "?:\Support\Ketarin" respectively). Is using "root" necessary to avoid the re-download problem?

OK I will check that. Maybe this is a problem that is already meant to be solved anyway.

{startuppath} is another option for how I use it, but since I was always using ".." to go up one directory, {startuppath} seemed redundant.

I've been testing it, works fine for me. I use the following path:

"..\Downloads\cdburnerxp-setup-{version}.exe"

When I use Ketarin on a different drive letter, it successfully locates the existing file and determines that no update is necessary. Can you please post the log for your case? Also I'd suggest to continue discussing this in the forum.

Answer
Declined

I'll close this for now since I do not see a issue here currently. If a specific problem occurs, I will fix it though (please post in the forum) since there shouldn't be any portability issues with Ketarin.