I guess it would be better to change help message about rebuild then. As of now, it says "Run this command after updating the fossil executable in a way that changes the database schema." So I would expect to see some information about such need in release notes. Perhaps it would be better to add to help that it is a good practice to run this command after each update. But then, why wouldn't rebuild happen automatically?
Pozdrawiam / With best regards, Orzech W dniu 13.12.2015 o 18:00, jungle Boogie pisze: > On 13 December 2015 at 05:12, Piotr Orzechowski <orz...@drzewo.org> wrote: >> I've just looked at release notes for 1.34 and 1.33 and there was no >> straightforward note about need to rebuild repositories. > > Admittedly I don't do it every time, but I thought that was something > to be done for every update? > > > Here's openBSD's port advising it's a good idea to run rebuild: > http://openports.se/devel/fossil > > After upgrading to a newer version of fossil, it is always a good idea > to run: "fossil all rebuild". Running "rebuild" this way is not always > necessary, but it never hurts. > > >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
