Subject:
|
Re: pictures at tracker
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Sat, 18 May 2002 10:27:19 GMT
|
Viewed:
|
1099 times
|
| |
|
|
In lugnet.cad, Steve Bliss writes:
> In lugnet.cad, Ross Crawford writes:
> > But we already know exactly when an image needs updating! Using make, you
> > still have to decide when to execute the make command, I'm saying the
> > obvious time to do it is when a file is submitted (update it's image and all
> > those which depend on it). You already have all the dependencies, and you
> > already know when an image needs updating, why do you need make?
>
> I have to disagree: we don't 'know' exactly when an image needs updating.
> We have the information needed to figure out which image(s) need updating,
> but it's in a form that still needs to be sorted through. Sorting through
> it isn't too hard, but it's still not trivial. It would be much less work,
> even from where we are, to spit out some make-style dependency files, and
> let make do the work.
What format are the current dependency files in, and when are they updated?
ROSCO
|
|
Message has 1 Reply:
 | | Re: pictures at tracker
|
| (...) They're in a tab-delimited text file, each line contains a super-to-subfile dependency, the status of the subfile - official, unofficial, or not found, and the title of the subfile. Like this: parts/3001.dat p/stud.dat official Stud The code (...) (23 years ago, 18-May-02, to lugnet.cad)
|
Message is in Reply To:
| | Re: pictures at tracker
|
| (...) I have to disagree: we don't 'know' exactly when an image needs updating. We have the information needed to figure out which image(s) need updating, but it's in a form that still needs to be sorted through. Sorting through it isn't too hard, (...) (23 years ago, 18-May-02, to lugnet.cad)
|
77 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
