Re: [Tei-council] TEI release directory structure

Thanks for asking, I did not want to bring it up myself ;) I think in former times, release added some value for making available various documentation of e.g. tei-emacs, or tei-roma (and probably the Stylesheets) under "/release/doc“ which was *not* found in the Vault. Now that we abandoned all this software and keep both Stylesheets and Guidelines in the Vault, the Vault has become the canonical location. „Release“ is a mere legacy structure which not much added value anymore. Yet, our own processing (which we could change) relies on this structure and other’s software might also. And of course, the canonical URL of the current Guidelines version is https://tei-c.org/release/doc/tei-p5-doc/en/html/ . While this is a clumsy URL, I wouldn’t dare to change it. But this might just be my unrevolutionary spirit … Best Peter

Am 01.03.2021 um 21:30 schrieb Martin Holmes :

Why is this release folder needed?

On 2021-03-01 11:48 a.m., Peter Stadler wrote:

...

Hi all, apologies for sending to both groups, but this issue is kind of between Council and infrastructure group, so I thought I’d be better to include both. The issue I see is about the „release“ directory structure, i.e. the stuff at https://tei-c.org/release/ Currently, on the Huma-Num server, „release“ is just a symlink pointing at "Vault/P5/current“ – this caused frequent errors with the Stylesheets release missing due to missing CSS files for building ePubs. It was hacked around by copying Stylesheets to P5 or symlinking Stylesheets into P5. Since the structure under „release“ seems to mimic the "/usr/share/doc“ and „/usr/share/xml“ structure known from Debian systems – and this is the place where the TEI Debian packages are installed by default – I think the *original* setup might have looked like an apache Webserver simply serving its local „/usr/share“ directory under „release“ to the outside. At the latest with the ADHO server crash, this setup got lost and we have a semi-functioning release directory now. IMHO, with our current infrastructure, the proper setup would be to (hard) create the directory „release/doc“ and „release/xml/tei“ and create symlinks within these directories to the respective directories in the Vault: release/doc * tei-p5-doc —> ../../Vault/P5/current/doc/tei-p5-doc * tei-p5-exemplars —> ../../Vault/P5/current/doc/tei-p5-exemplars * tei-xsl —> ../../Vault/Stylesheets/current/doc/tei-xsl release/xml/tei: * Exemplars —> ../../../Vault/P5/current/xml/tei/Exemplars * Test —> ../../../Vault/P5/current/xml/tei/Test * custom —> ../../../Vault/P5/current/xml/tei/custom * odd —> ../../../Vault/P5/current/xml/tei/odd * schema —> ../../../Vault/P5/current/xml/tei/schema * stylesheet —> ../../../Vault/Stylesheets/current/xml/tei/stylesheet * xquery —> ../../../Vault/P5/current/xml/tei/xquery release/oxygen —> Vault/P5/current/oxygen Does that make sense? Anything I’m missing? And of course, I’m curious about some more history that Lou(?) or James(?) might be able to share? Best Peter _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

-- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council