new packages not pulled if named the same
Issue #150
closed
If a package in the packages folder gets replaced by a package with the same name, it will not replace the existing package when saving to volume. Maybe keep track of a hash or even time stamp to see if it needs replaced.
Comments (6)
-
-
-
assigned issue to
timothy perfitt
If a package in the packages folder gets replaced by a package with the same name, it will not replace the existing package when saving to volume. Maybe keep track of a hash or even time stamp to see if it needs replaced.
-
assigned issue to
-
what do you think of an option like “full rebuild” instead of validation of if the packages are the same? It would just overwrite all the files. Would take a bit longer but would be much cleaner.
-
reporter
full rebuild leaves nothing to guesswork. Hate to clutter up the interface for something most people may not be affected by though.
-
- changed status to resolved
Please verify and close. Fixed in build equal to or later than: 60065
-
- changed status to closed
- Log in to comment
I am worried about calculating hashes on slow drives. I could calculate the hash on save and save it as an extended attribute and then compare to the original. Or I could just check the filesize, but that seems less reliable.