[
https://issues.apache.org/jira/browse/SVN-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498300#comment-17498300
]
Daniel Shahaf commented on SVN-4889:
------------------------------------
I haven't fully digested that thread yet, but:
For a low-level flagging mechanism, how about adding a boolean column to the
WCROOT table and unconditionally set it to TRUE upon upgrade, but for existing
wc's only activate the new codepath if the new boolean is set? That is, an f32
wc with the boolean manually set to FALSE would behave identically to an f31
wc? This shouldn't be much effort, and it would avoid hairiness later on ("I
don't want optional pristines, so I need to ensure my wc's are _either_ format
31 or older _or_ format 33 and have the knob set to the default value, but I
must error out if I see any f32") and, as mentioned, would let 1.15
interoperate with a potential future 1.16.
> Pristines-on-demand: per-WC config
> ----------------------------------
>
> Key: SVN-4889
> URL: https://issues.apache.org/jira/browse/SVN-4889
> Project: Subversion
> Issue Type: Improvement
> Reporter: Julian Foad
> Priority: Major
>
> [dev@
> thread|https://lists.apache.org/thread/qw2cngzc22kvzw8ro77jfqpoz9nhm3fx]
> "[PATCH] Sketch of per-user/per-wc config for pristines-mode"
> The #SVN-525 feature (aka WCs without pristines, pristines-on-demand,
> bare-WCs) needs a per-WC configuration capability.
> The thread linked above sketches one way of going about such a configuration.
> Other ways are possible too.
> This is not strictly needed for the first release or "minimum viable product"
> (MVP) of the #525 feature, as the feature can be activated by upgrading the
> selected WCs to 1.15 format and will default to remaining disabled for other
> WCs.
> It MIGHT be good to add the low level flagging mechanism now, because that
> might help any future new WC capability to co-exist in a 1.15 format WC.
> Otherwise any such new capability would have to assume that
> pristines-on-demand is always enabled in a 1.15 format WC, and so have to
> bump to another new format to make it optional. It is not clear which would
> be more effort.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
