setoolkit-developer

[SEToolkit-developer] How to handle orcallator

[Alex K. <ale...@gm...>]

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'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.

In addition orcallator.se uses the renamed orca_... versions, whereas
we have all the changes in those now, so we could swap back. Do we
still need all the 3.x versions of SE support in orcallator? 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), 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.:

${SE} -I${ROOTDIR}/lib/SE/3.4 ${OPTIONS} ${ROOTDIR}/lib/orcallator.se
${INTERVAL} </dev/null >/dev/null 2>&1 &

Maybe we ought to take this to the orcallator mailing lists?

-- 
Alex Kiernan

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

Re: [SEToolkit-developer] How to handle orcallator

[Alex K. <ale...@gm...>]

On 14/06/07, Dagobert Michelsen <da...@ba...> wrote:
> 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.
>

My thinking was really that workinfo_class.se is generic functionality
which could be used outside orcallator (for example it would be useful
to add it into zoom).

> > 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.
>

I think that'd be useful - I don't have contact details for him.

> > ${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?
>

Yup.

-- 
Alex Kiernan

Re: [SEToolkit-developer] How to handle orcallator

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

Hi Alex,

Am 15.06.2007 um 10:07 schrieb Alex Kiernan:
> On 14/06/07, Dagobert Michelsen <da...@ba...> wrote:
>> 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.
>
> My thinking was really that workinfo_class.se is generic functionality
> which could be used outside orcallator (for example it would be useful
> to add it into zoom).

That's a point. It should be pulled in when zoom.se is updated.
I opened a tracker for this:
   http://sourceforge.net/tracker/index.php? 
func=detail&aid=1737679&group_id=189279&atid=928692

>> > 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.
>
> I think that'd be useful - I don't have contact details for him.

Could you describe in a technical view what exactly the problem is?
Richard is quite busy and a good prepared question would help in
getting an answer ;-) If you want I can send you his address or
forward your request as you like.

>> > ${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?
>
> Yup.

I am looking forward the discussion :-)


Best regards

   -- Dagobert

-- 
"Of course computer servers don't need thrust, since they generally
don't go anywhere."  -- Comment in TR on new HP server turbine fans