On Sun, Sep 6, 2015 at 8:13 PM, Richard Hipp <d...@sqlite.org> wrote:
> On 9/6/15, Scott Robison <sc...@casaderobison.com> wrote: > > I was doing a little fossil hacking today and went to build it on my > > freebsd box and it failed because the manifest was not present. Is there > a > > reason why we haven't created a manifest versionable setting? It seems > like > > an obvious one for the project to have. > > > > Are there any projects (other than Fossil itself, and SQLite) that use it? > > Note that the manifest setting is copied whenever you clone. So it is > not clear to me how you ended up with a repo that had it turned off. > Can you elaborate? > Good point. Not a big deal then. As to how it happened: I have a little home grown project hosting setup that I've talked about before. Just a few PHP web pages that sit in front of my fossil repositories. One of the pages allows me to copy the existing configuration from a "template" repo to all my other repos. I was testing functionality after moving the webpages to a new computer and obviously overwrote the setting in my fossil clone from another repo without realizing it. -- Scott Robison
_______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
