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). 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. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
