Re: [SEToolkit-developer] How to handle orcallator

[Dagobert M. <da...@ba...>]

Hi Alex,

Von "Alex Kiernan"  (Thu, 14 Jun 2007 13:19:36 +0100):
> We discussed this briefly before and decided to leave orcallator out
> of se (which I still think is the right decision), but I'm wondering
> if workinfo_class.se is really part of SE toolkit rather than
> orca/orcallator?

I doubt that. It is only included in orcallator.se.

> I'm trying to figure out how to go about deploying orcallator
> (internally) against an updated SE toolkit, and what to do with the
> updated includes which orcallator ships with. We've merged all the
> changes, but not taken workinfo_class.se across.

Because it is used nowhere in se I see no problem in
leaving it in orca.

> In addition orcallator.se uses the renamed orca_... versions, whereas
> we have all the changes in those now, so we could swap back.

We could, but that change should be done at orca.

> Do we
> still need all the 3.x versions of SE support in orcallator?

IMHO no. But again this is an orca issue.

> ISTR they
> were there because of support getting dropped for various OS versions
> - looks like 3.0 was the last version to support 2.5/2.5.1 (and my
> efforts to put it back came unstuck when I hit /proc support)

Maybe we should ask Richard in this matter.

> , whereas
> I think we've all the pieces to allow a build on 2.6 and later.
> 
> FWIW as a quick fix I'm just hardcoding lib/SE/3.4 for the includes
> dir at the moment, i.e.:

...or just link 3.5 to 3.4

> ${SE} -I${ROOTDIR}/lib/SE/3.4 ${OPTIONS} ${ROOTDIR}/lib/orcallator.se
> ${INTERVAL} /dev/null 2>&1 &
> 
> Maybe we ought to take this to the orcallator mailing lists?

Yes. All the issues should be discussed there. Do you prepare a posting?


Best regards

  -- Dago