deadsoul / dugu Goto Github PK

It's possible I missed it but it looks like dugu read/writes to /tmp/dugu_root and this isn't documented.

I can't see an option to change this behavior (I've not debugged build_path())

If a relative path used when cache is generated, the cache won't be available unless the same relative path is being called in the next scan.

for example (first scan):
we're in /home/deadsoul/Documents, and we would like to scan /home/deadsoul/Pictures:

dugu scan ../Pictures

if we repeat dugu scan ../Pictures it should take advantage of the generated cache.
But if we're in /home/deadsoul and tried to dugu scan Pictures it will re-generate another cache. since '../Picutres' is not equal to 'Pictures'. which means dugu scan /home/deadsoul/Pictures should generate another cache.

and the same thing should apply if the scanned target directory is a link.

Suggested solution:
convert the given target-directory to its absolute path.

if there is any broken symlink in DIR1 (source_dir)
dugu will fail when using the argument precopy

it takes long time because the time is being wasted in copying the whole DIR1 !!

the way precopy works now is:

1. copying the whole DIR1 to DIR1/_UniqueFiles_
2. exclude the existing files in DIR2 from DIR1/_UniqueFiles_ by removing them

while it should be like

1. copying only the directory structure of DIR1
2. copying only the unique files

because we're wasting time by copying all the files, then removing some of them. instead we should only copy unique files

Need to check which counter is correct. is it the one in caches, or the one used to compare the cached one!
commit: caba8a2

It would be great if I could install this package with python3 -m pip install dugu, and then run it with python3 -m dugu -h. Please publish this package to the PyPI package index!