ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: tempdir support in texexec.rb
Date: Tue, 18 Jul 2006 11:50:10 +0200	[thread overview]
Message-ID: <44BCAED2.5040606@wxs.nl> (raw)
In-Reply-To: <44BCA352.2050509@tttech.com>

Matthias Wächter wrote:
> On 18.07.2006 10:29, Hans Hagen wrote:
>   
>>>> if it's because of the temp files. you can run with --purge and get them 
>>>> removed
>>>>         
>>> Well, then Context could not benefit from "incremental" builds with just one run instead of 4 to 5 runs. But I get the idea.
>>>       
>> eh ... the tuo file is kept
>>     
>
> Appearantly, only mpgraph.mp is removed by --purge, and --purgeall only gives some CtxTools help messages. Hmm ...
>
>   
>>> Maybe for this task, --purge is reasonable enough. I'll give it a try.
>>>   
>>>       
>> that's indeed the best way to go; btw, here i only version tex files 
>>     
>
> Depending on the process you have to maintain (you know, I mentioned Context version numbers before ...), you want to version everything except stuff that is there and unversioned by intent. At least you want to get warned of new files you may have forgotten to put under revision control, and as said, you may want to mark the document tainted because of unclean checkouts. The easiest approach would be to have a separate directory for non-output related stuff like .tmp, .log, .tui, .tuo, .mp, then any other unversioned file would be a sign of unallowed modification.
>
> OK, I will simply mark *.tmp, *.log, *.tui and *.tuo as "ignore".
>   
in ctxtools you can find a more detailed list (*-mpgraph *-mprun, 
*..mpt, *.mpd, etc)
> What's the difference between mpgraph.mp and <project>-mpgraph.mp ? The latter is not removed when using --purge. Is this by intent? Then I have to put *-mpgraph.mp to the ignore list, too.
>   
after we introduced the mpgraph name there suddenly apeared a similar file in the metapost paths; so, in order to prevent loading of that file by mistake, (e.g. when not using the prefixing) i create an empty one in the current path. the -mpgraph.mp plays a role in determining multiple runs when not in runtime graphics mode, but it does not need versioning 

Hans  


-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

  reply	other threads:[~2006-07-18  9:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17 14:23 Matthias Wächter
2006-07-17 19:35 ` Hans Hagen
2006-07-18  7:38   ` Matthias Wächter
2006-07-18  8:29     ` Hans Hagen
2006-07-18  9:01       ` Matthias Wächter
2006-07-18  9:50         ` Hans Hagen [this message]
2006-07-18  9:51         ` Hans Hagen
2006-07-18 10:40 ` Mojca Miklavec
2006-07-19  9:43   ` Hans Hagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44BCAED2.5040606@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).