ORBit2 release problems [Re: ORBit2 foo ...]

[Mark McLoughlin <markmc redhat com>]

Hi Tor,
	So, Alex just points out this:

  http://bugzilla.gnome.org/show_bug.cgi?id=315294

	I think this is the current situation we have:

  - The latest ORBit2 tarball released is ORBit2-2.12.3 from the 
    gnome-2-10 branch

  - There has been no release from ORBit2 HEAD

  - Michael seems to suggest that the plan was to ship GNOME 2.12 with 
    ORBit2-2.12 (i.e from the gnome-2-10 branch)

  - The GNOME 2.12 jhbuild moduleset uses ORBit2 HEAD

  - ORBit2 HEAD has a new macro - ORBIT2_MAYBE_CONST - which the 
    orbit-idl generated code uses

  - Because most maintainers have been using jhbuild, and hence jhbuild 
    HEAD, tarballs released with orbit-idl generated code are using
    ORBIT2_MAYBE_CONST and won't build with ORBit2-2.12.3

	Our options are:

  1) Release ORBit2 from HEAD and use that for GNOME 2.12

  2) Put ORBIT2_MAYBE_CONST on the gnome-2-10 branch and release 
     ORBit2-2.12.4

	(2) is probably the best option because ORBit2-2.12 is the better
tested codebase.

	Comments anyone?

Cheers,
Mark.

On Sat, 2005-08-13 at 11:40 +0300, Tor Lillqvist wrote:
> michael meeks writes:
>  > Just committed a fix for a nasty nasty to ORBit2 HEAD, and wondering
>  > what branch what is on ;-) eg. it seems we're basing Gnome 2.12 on
>  > ORBit-2.12 or whatever: which sounds good,
> 
> The gnome-2-10 (ORBit 2.12) branch has at least one Win32-related
> change (introduced before the branch) that wasn't really good and
> since got reverted in HEAD. I mean the dropping of "const" in some
> headers and IDL-generated code. It was later reverted in HEAD (and the
> ORBIT2_MAYBE_CONST macro introduced instead). (See bug #169428.)
> 
> Although I don't know how important that constness would be, as the
> bug report comments suggest that it doesn't give much space saving.
> 
> Anyway, the patch that introduces ORBIT2_MAYBE_CONST probably should
> be applied to gnome-2-10, better late than never?
> 
> --tml