ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
* Feature request: Timestamps
@ 2002-06-23 12:26 Patrick Gundlach
  2002-06-23 22:15 ` Hans Hagen
  0 siblings, 1 reply; 3+ messages in thread
From: Patrick Gundlach @ 2002-06-23 12:26 UTC (permalink / raw)


Hello ConTeXt hackers,

I would like to suggest to make some changes:

since some of the context files (the files in texmf/tex/context/base)
change once in a while, it would be nice to see which of them have
changed. The versioning info in the file should be updated according to
the last modified timestamp (if ther are any changes within the macros
or the doc only, of course).

Then it would be nice to have a web page with all the file listed in
base together with their timestap. it can be a simple 'grep':

something like this:

xtag-exp.tex:%D        version=2001.08.20,
xtag-ext.tex:%D        version=2001.03.21,
xtag-ini.tex:%D        version=2000.12.20,
xtag-map.tex:%D        version=2000.12.20,
xtag-mmc.tex:%D        version=2000.12.20,
xtag-mml.tex:%D        version=2000.12.20,
xtag-mmp.tex:%D        version=2000.12.20,

this would help to see if I need the newest beta, if i find a bug in
context in a certain file. For example, I am just checking the
core-itm for Idris, but I am note sure if the bug (if it is a bug) i
have found is still in the newest beta. Before downloading the whole
new cont-tmf.zip it would be nice if I could check a page on the web
and see if there are any changes.

Or put all your file into cvs and give us read-access :)

Patrick

-- 
I'll fade into the darkness


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Feature request: Timestamps
  2002-06-23 12:26 Feature request: Timestamps Patrick Gundlach
@ 2002-06-23 22:15 ` Hans Hagen
  2002-06-24  8:20   ` Patrick Gundlach
  0 siblings, 1 reply; 3+ messages in thread
From: Hans Hagen @ 2002-06-23 22:15 UTC (permalink / raw)
  Cc: ntg-context

At 02:26 PM 6/23/2002 +0200, Patrick Gundlach wrote:
>Hello ConTeXt hackers,
>
>I would like to suggest to make some changes:
>
>since some of the context files (the files in texmf/tex/context/base)
>change once in a while, it would be nice to see which of them have
>changed. The versioning info in the file should be updated according to
>the last modified timestamp (if ther are any changes within the macros
>or the doc only, of course).
>
>Then it would be nice to have a web page with all the file listed in
>base together with their timestap. it can be a simple 'grep':
>
>something like this:
>
>xtag-exp.tex:%D        version=2001.08.20,
>xtag-ext.tex:%D        version=2001.03.21,
>xtag-ini.tex:%D        version=2000.12.20,
>xtag-map.tex:%D        version=2000.12.20,
>xtag-mmc.tex:%D        version=2000.12.20,
>xtag-mml.tex:%D        version=2000.12.20,
>xtag-mmp.tex:%D        version=2000.12.20,
>
>this would help to see if I need the newest beta, if i find a bug in
>context in a certain file. For example, I am just checking the
>core-itm for Idris, but I am note sure if the bug (if it is a bug) i
>have found is still in the newest beta. Before downloading the whole
>new cont-tmf.zip it would be nice if I could check a page on the web
>and see if there are any changes.
>
>Or put all your file into cvs and give us read-access :)

i admit that i need to adapt the dates (but since i seldom work at the top 
of the file ...

Once i got out local infra structure updated (just installed yet another 
server which does auto backup using secure rsync) i will khave a look at 
it; one reason for not using a cvs repository (i would only use it as 
repository for public context stuff since i hate the idea of all kind of 
mess ending up in there) was that i was in the process of splitting up 
context (i'm still not sure what happens when one removes a file). So, 
there will be either a cvs or rsyncable archive (synced with our local web 
server).

Another option is to auto-update the time stamps (ignoring comment lines) 
which is what i already do with the main file.

So, it will happen (i will also provide a mechanism in texexec to use 
multiple context trees in parallel)

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Feature request: Timestamps
  2002-06-23 22:15 ` Hans Hagen
@ 2002-06-24  8:20   ` Patrick Gundlach
  0 siblings, 0 replies; 3+ messages in thread
From: Patrick Gundlach @ 2002-06-24  8:20 UTC (permalink / raw)


Hans Hagen <pragma@wxs.nl> writes:

Hi,
> >Or put all your file into cvs and give us read-access :)
> 
> i admit that i need to adapt the dates (but since i seldom work at the
> top of the file ...

Your editor should do this for you :)

> a file). So, there will be either a cvs or rsyncable archive (synced
> with our local web server).

I like the idea of being able to download just a few file and have a
recent context :)

> So, it will happen (i will also provide a mechanism in texexec to use
> multiple context trees in parallel)

I have several context trees installed in parallel. I switch between
them with only one command, which sets all the necessary environment
variables. 

Patrick

-- 
I'll fade into the darkness


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-06-24  8:20 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-06-23 12:26 Feature request: Timestamps Patrick Gundlach
2002-06-23 22:15 ` Hans Hagen
2002-06-24  8:20   ` Patrick Gundlach

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).