Andrew Borley wrote:
Hi Oisin,
On 10/4/06, Oisin Hurley <[EMAIL PROTECTED]> wrote:
Hi guys,
Sorry I couldn't make the IRC - had to run off to a night class.
> 18:36:06<ajborley>what about MacOSX? there was a patch for that,
> but I don't
> know what the status is
> 18:36:17<ajborley>I also don't have access to any mac machines
> 18:36:19<robbinspg>I'll do Mac OSX
> 18:36:32<robbinspg>so long as someone buys me a new PowerBook
> 18:36:47<jsdelfino>for MacOSX the first question is: is Axis2C
> shipping bins
> on MacOSX?
I can get a MacOSX build done for 0.94, but as you can see at [0], the
priority on the patch is low. Looking at the current set of Jirae that
are going in there it seems they have more pressing concerns.
This brings up a question from me wot is ignorant of Apache devoirs
in term of infrastructure support. Since I'm mostly doing Eclipse
work, I'm used to having heaps of donated build machines that will
do nightlys etc. I guess that this is not the case at Apache and
that binary builds are done by project committers - or the most
excellent release person :)
Yep, that's right. I assume at the moment that there is no-one working on
Mac OSX in Axis2C - I'm sure they would be very happy to have Mac OSX
coverage if someone can provide the build & testing work.
I will update the Axis patch to work with the current pre-0.94 base
and see will they take it (it's not a new feature imho).
That would be good - we decided near the end of the IRC chat to have a
dependency on Axis2C 0.93 as we weren't sure exactly when 0.94 would
be out
and we'd like our first RC by the end of this week. Saying that,
Sebastien
put in a tiny code change which made Tuscany work with the latest Axis2C
trunk, so the 0.94 release will hopefully work with Tuscany M2.
If they don't, would it be a horrible gaffe to post an 'independent'
set of binaries and headers as a supplemental download on the
Tuscany site? I hope asking that question wasn't of itself a
horrible gaffe :)
I have no idea - I'm not sure if the Tuscany site is the best place to
host
an Axis2C MacOSX binary, but we could certainly point to one on another
(perhaps independent?) site. Another option is to point to/provide the
patches to enable OSXers to build Axis2C and then Tuscany.
+1, if there's no better option then I think we should at least provide
the patches and instructions to build Tuscany and its dependencies on
MacOSX from source. Many people in open source communities now use
MacOSX and without a MacOSX build they won't be able to work with
Tuscany C++ at all. With all the effort that Oisin already put into it,
I think it makes sense to at least publish these instructions and make
clear that people can download our source distro and follow these
instructions to build on MacOS X.
18:36:50<ajborley>:) do we want RC1 on OSX? Could anyone volunteer?
> 18:37:12<ajborley>Good point - I doubt it
> 18:37:22<robbinspg>let's get RC1 out and see if the resulting src
> release
> can be built on Mac
> 18:37:36<jsdelfino>we should ask oisin what he wants to do, since he
> contributed that patch and tested it
Consider me volunteered for build and test - I would consider that
there is more important work to be done for RC1, so I'm not going
to be insistent on it's inclusion.
Cheers Oisin, that's great - I guess we won't have the time to get it
into
RC1, but we may be able to sort it out for a later RC.
Great Oisin, thanks! As I said above I think it's really important to
have a MacOS X build for all the MacOS X open source developers out there.
Thanks!
Andy
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
