To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.rayOpen lugnet.cad.ray in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Ray-Tracing / 32
31  |  33
Subject: 
Re: Partsref is Moving to LUGNET
Newsgroups: 
lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray
Date: 
Fri, 3 Dec 1999 17:52:40 GMT
Viewed: 
29 times
  
In lugnet.cad.dev, Larry Pieniazek wrote:

Steve Bliss wrote:

One problem with make is that sometimes, the image file will be based on an
outdated DAT, but the image will still have a more recent datestamp than the
current DAT.  And make can't deal with that (unless someone changed make and
didn't tell me).

This is kludgy but might work. Details left as an exercise. Your problem
is that what you want is to know when a file is *new to YOU* not what
it's timestamp is.

I'm going to need to keep a vanilla installation, just for partsref generation.
It's too tempting to make minor edits to part files in my regular installation.
And, if I'm going to have two copies of LDraw, I'd rather have "working" and
"partsref" than "original" and "touched".

Hmm.  How about this:

Receive new update file.
Expand new update, in a temp directory.
Touch all files in temp directory.
Copy files from temp to partsref copy of ldraw.
Make partsref.
Don't touch partsref copy of ldraw before next update.

Steve



Message is in Reply To:
  Re: Partsref is Moving to LUGNET
 
(...) This is kludgy but might work. Details left as an exercise. Your problem is that what you want is to know when a file is *new to YOU* not what it's timestamp is. Keep two complete sets of .dat files. One is an image of the state of files, but (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)

32 Messages in This Thread:









Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR