From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/9302 Path: main.gmane.org!not-for-mail From: Tobias Burnus Newsgroups: gmane.comp.tex.context Subject: Re: getting context's version Date: Wed, 18 Sep 2002 11:17:33 +0200 Sender: owner-ntg-context@let.uu.nl Message-ID: <3D8844AD.6F42272D@gmx.de> References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035399643 2157 80.91.224.250 (23 Oct 2002 19:00:43 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 19:00:43 +0000 (UTC) Cc: ntg-context Original-To: Wybo Dekker Xref: main.gmane.org gmane.comp.tex.context:9302 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:9302 Hi, Wybo Dekker schrieb: > > the method that taco posted is the way to go, since it's in the main > > context file that i (when zipping) change the version number > > except that, if you unzip the newest cont-tmf and do mktexlsr but forget > to regenerate the format, it tells that the new version is there, but the > old one is actually run. How about: - check whether cont-en.efmt is older than context.tex If this is the case, issue a warning/error - check the version in context.tex This catches also buried problems like fmt file older than texmf tree which can also produce strange errors. (e.g. with cont-new.tex). > So if I try to make a fool-proof script that needs the newer version, it > would be nice to have the version from the format itself. well using cont-en you got this number, unfortunally the fmt file is a not that easily readable memory dump so you cannot easily grep for the number directly without using TeX. Tobias -- This above all: To thine own self be true / And it must follow as the night the day / Thou canst not then be false to any man.