--copy-chunker-params question on future deduplication if not initialised from the beginning

restic 0.19.1 compiled with go1.26.4-X:nodwarf5 on linux/amd64

I made a new repo. Say that I did not use “restic init --copy-chunker-params”, but just made a new repo… THEN, I backup a snapshot from a already backed up snapshot using (–from-repo). I realise that I may not get full deduplication… but is there any way in the future to gain back deduplication (in future backup/snapshots) when I for example go into older snapshots and delete files I don’t want anymore, and then use commands such as “prune”, and “forget” (if in fact I decide I no longer want those previously backed-up files?), and then the newer made repo will also copy the newer snapshot and realise that there are (were(past tense)) deleted files, and then I can run “prune” and “forget” on the newer made repo (the newer one without the “restic init --copy-chunker-params”), and it will just prune the older files anyway, so kinda it does not matter if I initiate the new repo with “restic init --copy-chunker-params”, but I can still deduplicate everything eventually by pruning and forgetting old files which I don’t want?.. Thanks everyone, if you understand my question… I can re-iterate or explain better if needed. Thanks!


long question, but short question is "I can always make a repository deduplicated as long as I use “prune”, and “forget”, right?.. even if I initially did not use the “–copy-chunker-params” on repo initialisation? (and used the copy --from-repo) command? Thanks if that was easier to understand…

…a further breakdown… I made a new repo… not with “–copy-chunker-params”. I use the “copy --from-repo” command to the new repo. I know it will not be deduplicated to the fullest, but if in the future I do a straight “backup” command… will it deduplicate?