On Jun 15, 2018, at 4:46 PM, Stephan Beal <sgb...@googlemail.com> wrote:
> 
> - refactoring to a lib is a huge effort.

That’s the real trick, I think: the library needs to be part of Fossil proper, 
so that it stays up to date.

That in turn means finding and maintaining a strong boundary between whatever 
your conception of “less Fossil” is from “whole Fossil.”

If such a clear boundary doesn’t already exist, refactoring Fossil until such a 
boundary appears will be difficult, but perhaps worthwhile on its own merits, 
even if your liblessfossil is never used.

More than once, people have proposed applications of Fossil that could use this 
liblessfossil, where arm-twisting whole Fossil into the role was not sensible.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to