Re: suggestion




HI Paul

I thought that I allowed for both types of run files in the code.  It did 
work here.  The if that does this is located about line 96 in 
Make_new_runset.  If it doesn't work, ship me the run that you tried it 
with and I'll work on it.

My thoughts when I wrote this proposed setup was not to eliminate either 
run or ini so that we had to depend on some gui based program to do the 
work of writing these files.  I'm with the fellow who said he'd sooner 
edit a file using a text editor than depend on point and click.  I am of 
the sort to take a stock file and cut out the verbage and the extraneous 
and save a streamlined copy for my own use.

BTW I do like the change in the way that the run works because it will 
allow us to update only one file in the repository for most users.  Next 
we need to weed out the emc versions and all of the others as well.

Thanks for looking at it.  I'm curious to know what went wrong.

Ray


On Wednesday 09 October 2002 04:41 pm, you wrote:
> Hi Ray
>
> The INIFILE fails to get changed within the new run file. Might I
> suggest that instead of copying *.run, a new one is generated from
> scratch. It need not be a complex affair -
>
> #!/bin/bash
> exec ./generic.run - ini $MYINIFILE
> exit 0
>
> Reasoning - If the generic.run gets updated to take account of a new
> driver, the changes do not have to be made in every run file. It is
> also a little easier to write a file than to grep and sed it.
>
> Regards, Paul.
>
> On Wednesday 09 Oct 2002 8:50 pm, Ray Henry wrote:
> > Snip this and Post your feelings about it.  If we decide it works,
> > I'll put it in the repository and we can begin to build other modules
> > for it. If you have mods, additions, ideas and you can't wait hack up
> > this and pass it around.




Date Index | Thread Index | Back to archive index | Back to Mailing List Page

Problems or questions? Contact