Den fre 11 mars 2022 kl 11:28 skrev Vincent Lefevre <vincent-...@vinc17.net >:
> On 2022-03-11 10:04:36 +0000, Julian Foad wrote: > > Daniel Sahlberg wrote: > > > I'm taking an opposite position with regards on where this should be > > > administred. [...] I would prefer a multi-level approach where the > > > repository (through svn:foo properties) could suggest pristine-less WC > > > > I understand completely your case, but the solution you need is a way to > > configure your client's behaviour remotely, and that is not necessarily > > best done by Subversion versioned properties. Do you see the > > distinction? Rather, what you need is for client configuration to be > > managed centrally and obeyed by your clients. The server and clients > > involved *could* be your Subversion repository server and Subversion > > clients, but could alternatively be some other mechanism. You just need > > some mechanism that works and is easy enough to deploy. > > If I understand what Daniel Sahlberg intends to mean is that the > property would actually tell the client what to do *by default*, > removing the need to configure the client. But I suppose that its > use would be very uncommon (say, for a repository storing only > big binary files, the main goal being to keep the history, but > where "svn diff" would never be done in practice). > Correct! Having such a property on directories and/or individual files would > be much more interesting, but in such a case, there should be more > than 2 levels of suggestion. > In our case we have directories with binary blobs of documentation and I would like to set it on that directory, but not on the directories containing source code. We also commit compiled code (identified by file name extension) and I would like to set it (via auto-props) on these files. Again: I'm not suggesting that Subversion should set such settings *by default* but provide a mechanism for the committers to set it. Kind regards, Daniel Sahlberg
