On Wed, Jun 17, 2020, at 13:45, Janne Johansson wrote: > Do think of what you call "the index file" in terms of "I check/replace some > 100+G of snapshots and packages every 24h", at which point do you replace > that single file, before, under or after none,most,all packages for your arch > are replaced? Will it be synced when the copying passes "i" for "index.txt" > in that packages folder? My gut is it doesn't matter when the file is sync'd. The file would only be used to prevent pkg_add from checking *every* installed package file *every* time. The effect would be basically the same as how my tool works, which is, it gives you a subset of installed packages to update, except with the added benefit of also detecting same-version rebuilds. pkg_add would still go through its normal recursive dependency checking, just with a (presumably) *much* shorter package list.
> What happens if a sync gets cut off, restarted and/or if two syncs suddenly > run into eachother and replace files as they go? > > What if a new batch of amd64/i386 files appears while one of the ongoing > syncs run, do you restart over and hope yet another new one doesn't appear > while that one is running? Is this something that actually happens?
