[Context] reporting changes in minimals
Hello, I'm rewriting the scripts for minimals-building (behing schedule, but well ... at the moment I'm a bit more worried about the exams than the conference). I figured out that I need a way to report any changes that might have occurred from one update to another (let's say that updating script figures out that a library has been renamed from kpathseaXYZ.dll to kpathseaXYW.dll and wants to report that change; in this particular case I will now go for "just include anything that ends with kpath*.dll"). The list would then be checked manually every now and then either by me or other volunteers - that would slightly reduce the risk of completely broken installations (for example when the Polish completely rename the font folders from "public" to "nowacki" etc, it would not to unnoticed until somebody gets a broken installation). One question - what way of reporting the changes is: - relatively easy to implement - even more important: easy to review (that is: no zillions of emails in mailbox) I would like to have a few different layers of importance (for example one full log that would tell me when some file has been changed; one file that would notify of new & deleted files, one log that would report errors etc., one report that would tell me "a new context beta is available", one report for "the basic test for minimals experimental has failed" etc.) PS for Taco: do we need the following two files frow W32TeX: - bin/lib/lua/bit.dll - bin/lib/lua/lxp.dll Mojca
On 09/05/2010 04:59 PM, Mojca Miklavec wrote:
PS for Taco: do we need the following two files frow W32TeX: - bin/lib/lua/bit.dll - bin/lib/lua/lxp.dll
Those are loadable lua modules (bitwise operations and XML expat). It does no harm to include them but they are not needed and do not exist in other platforms nor in the luatex distribution. Best wishes, Taco
On Sun, Sep 5, 2010 at 17:39, Taco Hoekwater wrote:
On 09/05/2010 04:59 PM, Mojca Miklavec wrote:
PS for Taco: do we need the following two files frow W32TeX: - bin/lib/lua/bit.dll - bin/lib/lua/lxp.dll
Those are loadable lua modules (bitwise operations and XML expat). It does no harm to include them but they are not needed and do not exist in other platforms nor in the luatex distribution.
Thanks. So I will leave them out until the first user requests them. Mojca
On 09/05/2010 04:59 PM, Mojca Miklavec wrote:
One question - what way of reporting the changes is: - relatively easy to implement
I used to have a shell script based on ls: ls -l ran before and after with output to disk, then I emailed myself a unified diff of the two files. Not so easy to review maybe, but very simple to set up. Best wishes, Taco
I used to have a shell script based on ls: ls -l ran before and after with output to disk, then I emailed myself a unified diff of the two files. Not so easy to review maybe, but very simple to set up.
Can't we use rsync to report the changes? Set up two directories, one with the older release and one with the newer one, and use rsync -av --progress --delete to copy the content of the newest version to the oldest one; rsync should generate a list of files to be added or deleted. Of course this has the drawback of temporarily needing two copies of the entire tree, but we then can take advantage of rsync's capabilities. Arthur
On Sun, Sep 5, 2010 at 17:47, Arthur Reutenauer wrote:
I used to have a shell script based on ls: ls -l ran before and after with output to disk, then I emailed myself a unified diff of the two files. Not so easy to review maybe, but very simple to set up.
Can't we use rsync to report the changes?
It should be doable in some circumstances, but not in others. For example, I cannot imagine using rsync to report that "web2c-2010-w32.tar.bz2" doesn't exist on Akira's server any more. When I think a bit ... the most elegant way to review the changes would be some JS-based HTML page where one could open & close "tabs" with changes (so that one still has), for example: - differences from Akira's server (4) (and then one can open it to see which files have been changes) - new versions of ConTeXt (3) (and then one can open it to see which versions have been uploaded) - fonts (300) (300 files have been changed; open to see which ones) but then it would take me too much time to figure out: - where to store the data (database?) - how to create a nice html with appropriate javascript Mojca
participants (3)
-
Arthur Reutenauer -
Mojca Miklavec -
Taco Hoekwater