On Sat, Nov 28, 2015 at 02:17:01AM -0800, Kornel Benko wrote: > Am Samstag, 28. November 2015 um 11:03:39, schrieb Georg Baum > <georg.b...@post.rwth-aachen.de> > > Scott Kostyshak wrote: > > > > > Does anyone object if I put this in Development.lyx? I will document how > > > to update the relevant files for each of the different formats. > > > > No objection, it is a good idea IMHO, > > +1
It is in at 0ee4dff4. If interested, please read and make corrections. The relevant sections are: - the last item in "How to update the file format number of .lyx files" - 2.3 Updating the file format number of layout files - 2.5 Updating the file format number of bind/ui files > > but for each recommended update there > > needs to be an automated way of doing it, e.g. a single command that does > > everything. Otherwise, it is too much burden. Agreed. Luckily because of Georg and Richard's work we have such commands. > The hazard here is, that it is too easy to update and commit without further > checking. Agreed. But I do not see any way to improve this situation. Currently, before releasing I update the format and although I do a (very) quick scan through the resulting diff, I really don't know what to look for except for things that look strange to me. At least now, if the authors do not look themselves we can look on the list (we will get an email about the commit) and ask about specific changes that seem strange. > The same reason holds for cmake targets like 'update-po' or > 'updatetex2lyxtests'. > > > Is there any update we cannot > > do automated (or where the automation is not platform independent)? > > I don't see problems for cmake. I believe that all is needed is python on bash. Scott
signature.asc
Description: PGP signature
