Re: [fossil-users] Suggestion for local/global settings enhancement

[Ron W]

This would be a very helpful enhancement.

On Sat, Dec 5, 2015 at 1:05 PM,  wrote:
>
> My suggestion is this:
>
> Have some form of shorthand notation – a text replacement macro, if you
> like – (like the string “~global~”, for example – or some other that is
> very unlikely to be an actual filename – or even something that is
> impossible to be a filename depending on the underlying OS), to let one
> import all the global settings for the given setting when specifying the
> local setting.
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Suggestion for local/global settings enhancement

[Ross Berteig]

On 12/5/2015 10:05 AM, to...@acm.org wrote:

Certain settings, like ignore-glob or binary-glob can have a really long
list of items, which may be edited from time to time.


This was the motivation for the invention of "versionable" settings, 
allowing the list to be maintained in a multi-line text file.



Ideally, the global setting should have the ones that apply to all
repos, while the local setting only the ones that apply only to that
specific repo.


IMHO, a repository should stand alone. It should provide all the 
specifications needed to work with and build. The "*-glob" settings are 
inherently project-specific, and could break scripts or other automation 
if they were changed unexpectedly. Specifying them completely as 
versionable settings minimizes that risk, and tracks them along with 
revisions of the project as a whole.


Global settings are for things that are obviously specific to a 
particular host and/or developer, and which need to be customized for 
each host and/or developer so that the repository works as intended. 
Settings like "proxy", any "*-command", and any described as providing a 
full pathname are obvious candidates for a global setting.



The problem is once you decide to use the local setting you need to
specify the whole long list of items again for each repo.  And if you
later change the global setting you need to remember to redefine all
local settings for repos that include more items in the same setting to
include the changes of the global setting.


I believe this is an intended effect.


My suggestion is this:

I hope I described this well enough to make sense.  I also hope you see
the usefulness of what I’m proposing.  (Well, at least if you normally
maintain more than just a few repos.)


It isn't too difficult to keep a reference set of default contents for 
the .fossil-settings folder and to write a site-specific script that 
tunes a new repository by copying in that folder and doing fossil add on 
it, and automating other customizations as needed.


--
Ross Berteig   r...@cheshireeng.com
Cheshire Engineering Corp.   http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users