On Wed, Apr 6, 2022 at 4:28 PM Julian Foad <julianf...@apache.org> wrote: > > Johan Corveleyn wrote: > > I think this was asked several times before, but I can't find the > > thread: is the pristines-on-demand behavior still unconditionally tied > > to format 32? Or is it that format 32 makes it _possible_ to enable > > pristines-on-demand? > > Currently it's tied to f32, but it's pretty clear it needs to be > uncoupled. The issue is: > > https://subversion.apache.org/issue/4889 "Pristines-on-demand: per-WC config" > > In principle we could address this later, only when a further new > version is released with a further new format and a further new feature > that users need to have available without enabling pristines-on-demand; > but it seems more responsible to uncouple it before we release it. > > I think that means #4889 is the other blocker issue. (Does anyone see > any way around it?)
Ah, yes, I think that makes #4889 a blocker. I tried to suggest a slightly more flexible per-WC-config than just a yes/no flag, but rather an open-ended "pristine strategy" or "pristine storage strategy" value (of which we would now introduces two options: "full" and "on-demand" / "lazy" / whatever) [1] [2]. But maybe that's overdesign without having an idea about what other "pristine storage strategies" might require in additional config details. [1] https://lists.apache.org/thread/h7xomovdclcm91vrskvj8kb0dbm1jng5 [2] https://lists.apache.org/thread/n3j50zv4sssqjcjfnz44ht5ho9p6db3f -- Johan
