Re: ORBit2 parallel install fixes
- From: Havoc Pennington <hp redhat com>
- To: Mark McLoughlin <mark skynet ie>
- Cc: <orbit-list gnome org>
- Subject: Re: ORBit2 parallel install fixes
- Date: 18 Sep 2001 17:18:36 -0400
Mark McLoughlin <mark@skynet.ie> writes:
> Ahh relax - we've always got ${includedir}/ORBit ;)
>
> Seriously, though - I don't think the change is needed and
> would be more trouble than its worth.
It's no trouble at all, I already did it. ;-)
I just realized there's a substantive issue. Note that we could not do
this:
gtk 1.2 includedir/gtk/foo.h
gtk 2.0 includedir/gtk-2.0/foo.h
we had to do:
gtk 1.2 includedir/gtk-1.2/foo.h
gtk 2.0 includedir/gtk-2.0/foo.h
You can do this:
orbit1 includedir/orb/foo.h
orbit2 includedir/orbit/foo.h
but not this:
orbit2 includedir/orbit/foo.h
orbit3 includedir/orbit-3.0/orbit/foo.h
you have to do this:
orbit2 includedir/orbit-2.0/orbit/foo.h
orbit3 includedir/orbit-3.0/orbit/foo.h
so we may as well go ahead and do an orbit-2.0 subdir right away, so
youu don't have to create this confusion during the stable maintenance
cycle. The orb/ to orbit/ strategy is a source-incompatible change that
causes a bunch of problems, so we really don't want to again change
what people have to put in their #include lines.
So I think it's wrong in a very-much-worth-fixing way to have
orbit/foo.h directly under includedir.
> orbit-idl2.h, hmm, I don't think we should be installing this
> for the moment. For one thing it includes headers that *aren't*
> installed. For another, I'm not even sure if idl compiler backends are
> working.
OK, I won't install it then.
> ORBitservices - I think these should go into orbit/services if
> no-one has objections. Oh, and there seems to be an IDL file in
> there...
I'm not sure exactly what you mean, but I think you mean something
that breaks people's current #include lines.
We can't put -Iincluddir/orbit-2.0/orbit in cflags, because that
breaks other things (it ruins the namespacing provided by the "orbit/"
in #include <orbit/foo.h>).
I think we should go with the orbit-1.0/orbit-2.0 scheme, it's what
every other package does, it's proven to work, and the work is already
done.
Havoc
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]