Re: Resource configuring

Hi,

Sorry about replying to an old thread, I'm somewhat behind with the
mailing list due to holidays and whatnot....

> > [I was thinking that for the mini-launch it might be handy to have a
> > complete sidai-like team. I'm willing to offer my own as a starting point
> > when(/if?) I get it all working.
>
> No objections from me... Of course, that's what glasli1 is
> (but it's not in public CVS).  And it doesn't get rebuilt
> from scratch.  (Michael would yell at us.)

It seems main teams {glasli1, ekbdt0, verilab1} are all very similar.
Perhaps we should either shunt some of the knowledge into sidai, or add
another level of indirection (ie. prototype) to encapsulate these
similarities. In particular perhaps the version specific stuff that is in
currently in team package files should be moved into sidai.

> Maybe there should be a way to have <dependency...>
> constraints without the "make it so" behavior. ???  Another
> attribute (besides type= and name=)...
>
>    action="check-only" or "make-it-so" (default)

Could we use have a third option of the form "check-only-and-continue",
which would allow us to continue looking down the prototype tree if the
required resource isn't there:

eg.

  <CC>
  <constraint action="check-only-and-continue">
  <host-spec>sidai:rhlinux</host-spec></constraint>
  <string>/usr/bin/gcc</string>
  </CC>

  <CC>
  <constraint action="make-it-so">
  <dependency type="essential" name="gcc"/></constraint>
  <string>/our/bin/gcc</string>
  </CC>

ie. use /usr/bin/gcc if it's there, otherwise force a build of gcc?

Matt