On Mon, Aug 31, 2015 at 7:27 PM, Warren Young <w...@etr-usa.com> wrote:
> > That becomes fossil's problem > > No, it’s the hook-writer’s problem. > > The hook-writer solves that in the normal way: log the problem so that a > human can figure out how to solve it, then retry the commit. > Hooks are not just about emails, but about policy decisions. "Does this file conform to XYZ." A failure at that level is unrecoverable without changing the policy. > > Many commercial/enterprise environments don't allow this. We once, after > 8 months of development using 'maven' as a build tool, had to port > everything to ant after discovering that the remote site does not allow > external internet access (in or out). > > How do you imagine such a problem could bite a Fossil user? > Now that you mention it... i can't, unless it allows inbound but no outbound traffic (one bank i worked at has some network segments set up that way). > Case 2: They have a perfectly working Fossil setup with hooks, then 8 > months later they move it to a new remote site, and it fails immediately > because none of the hook scripts will run. Now they get to choose whether > to disable hooks or solve the site restriction. Solve == remove, as the code is already committed and fossil disallows history changes. > If they choose the first option, Fossil goes back to working the same > way it does everywhere else, which I think we can agree to summarize as, > “Adequate,” at the least. :) > Adequate, but troubling nonetheless. > Hooks are optional. They may add site-specific restrictions, but > bypassing these restrictions does not harm the Fossil DB. > Not the db, but the constellation. They leave the "violating" user in a state which is no longer mergeable with the main repo. > I imagine some people will try to use hooks to create inviolable > constraints, but that’s predicated on those hooks actually running, and not > being bypassable. That’s purely a local administration problem, not > something that the Fossil project has to solve. > Agreed, but this list is the first place they'll run when such a policy forks them from their main repo, asking for advice on how to solve it. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
