Open martindholmes opened 8 years ago
Thank you @martindholmes ! This situation seems like something we'd better try to deal with quickly. Is there anyone here with, er, the keys to OxGarage?
I've just emailed you and a couple of other people with what I think might be the answer to this; perhaps we can try it.
Why not put "the answer" on this ticket?
It involves a discussion of filepaths and setup on a specific server, so it doesn't really belong here.
Updating it (as per email discussion) should just be a matter of running the tei-install.sh script with a slightly different set of options. I think it should be the release manager's job to do this (since they are there anyway doing it for the TEI Guidelines release).
Please don't move this issue to the OxGarage repo, because the heart of the problem is that no-one is paying attention to the OxGarage repo.
Roma depends on OxGarage to do its schema generation, and OxGarage depends on having an up-to-date copy of the TEI Stylesheets to match the version of P5 which Roma is using. Roma's P5 database is always updated as part of the release process, but there is no procedure defined for updating OxGarage, and it hasn't happened for a long time; as of the release of P5 3.0.0, Roma now fails to produce working schemas.
Since Roma is not going away, and there's nothing fundamentally wrong with how things are supposed to work, I believe the TEI release process for both the Stylesheets and P5 should include a step by which the installation of the TEI Stylesheets is updated on OxGarage. I don't know whether the current version of OxGarage is running at Oxford still or is on the TEI server, so I don't know how this could best be done, but it needs to be done. I'm raising the issue so that it doesn't get forgotten.