Re: [Orca-robotics-devel] Orca Objects

[Alex B. <a.b...@ac...>]

On Fri, 2004-07-23 at 16:16, Tim Arney wrote:
> Provided they install cleanly, I don't think there's a problem with 3 packages. 
> I imagine by the time we have a user base Orca will be reasonably mature so
> that generally components won't break when the base packages change, and major
> base ugrades will be less frequent.
> 
> I think a better alternative though, but I have no idea whether this is
> possible, is to pull anything that's replicated across orca-base-xxxx back into
> orca, and if that's possible, put the abstract object definitions in orca as
> well.  Would that create some kind of unmanageable circular dependence?

Yeah, that circular dependancy is the problem.  Somehow you have to
build orca-base-xxxx, but this is only possible if the common stuff is
available.  And somehow you have to build orca, but this is only
possible if orca-base-xxxx has been built.  You could do something
really dodgy like expect the two packages to be un-packed side-by-side
and have them reference one-another, but this is bound to cause
confusion.

Alex