Update (I know you've been on the edge of your seat for this one): The AGU LaTeX maintainers thought that file names were case insensitive. The FTP files were updated so that now both sources have the same files _except_ that one is named AGUTeX.cls and the other is named agutex.cls. I'm trying to convince them that file names are case sensitive for some file systems and to rename everything to the lowercase name. If they do this, I will revert my commit (and JMarc's fix of my commit).
Scott On Tue, Aug 20, 2013 at 4:26 PM, Scott Kostyshak <skost...@lyx.org> wrote: > On Tue, Aug 20, 2013 at 3:57 PM, Scott Kostyshak <skost...@lyx.org> wrote: >> On Thu, Aug 15, 2013 at 1:57 AM, Scott Kostyshak <skost...@lyx.org> wrote: >>> The cls has changed case and thus breaks compilation of the template. >>> >>> The old file is still there: >>> ftp://ftp.agu.org/journals/latex/journals/Manuscript-Preparation/ >>> >>> but I contacted the journal (la...@agu.org) and was told to use the newer >>> one: >>> http://publications.agu.org/files/2013/03/AGU-LaTeX.zip >>> >>> The new one is also the one pointed to by the journal's LaTeX guide: >>> http://publications.agu.org/author-resource-center/author-guide/latex-formatting-toolkit/ >>> >>> Should we change to the new case? >> >> Committed at 66dfbab and I added a note on the wiki page to explain >> that if you are using LyX 2.1 or later, the new link is different: >> >> Scott > > This will break old documents (.lyx files created with the previous layout). > > We could create a new layout agutex_old.layout (we need the suffix > '_old' because some file systems aren't case sensitive) and then have > lyx2lyx translate using 'agutex.layout' to using 'agutex_old.layout'. > Would that work? > > Another option is that I could revert the commit I just committed. I > looked at the diffs of the .cls files and they are minimal. I could > revert the commit and we could wait until the old ftp files are > removed or until there is a meaningful change in the new .cls file. > However, it seems best to deal with this now (a major version change) > rather than wait. > > Have we come across a similar issue before that I could look at? > > Scott
