Hi Berin,
If you want put in some Makefile patches, that's fine with me. We tend to
break the zOS build every release anyway, so it's not a big deal.
Dave
Berin Lautenbach
<[EMAIL PROTECTED] To: Xalan C Users
<[email protected]>
om.au> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: Re: Impending 1.6
release
07/15/2003 12:04
AM
Bjoern,
Mea culpa - I was going to look at this.
David - are you comfortable for me to integrate into CVS on the weekend?
It _might_ break some other things (namely OS390), so it might delay
1.6 a bit. But I reckon it's worth doing, and I'm getting no closer at
all to taking a proper look at the configure system.
Thoughts?
Cheers,
Berin
Bjoern A. Zeeb wrote:
> On Mon, 14 Jul 2003 [EMAIL PROTECTED] wrote:
>
> Hi,
>
>
>>It's about time we do a 1.6 release, for compatibility with Xerces-C 2.3.
>>So, if there are any open bugs you would like fixed before the release,
or
>>there's anything you're looking for, please speak up now.
>>
>>It would be great to get the release out at the end of this week, or the
>>beginning of next.
>
>
> thanks for the information; so I will wait with submitting the FreeBSD
> port to freebsd gnats until the update.
>
>
> Just for being stubborn ;-) - ist there any chance for make install
> target to make it in after (or before) the release. I'd vote for just
> after to not bring in new problems while in release building process ?
> Did on of the people with OS390 access test if the patch breaks the
> building process ?
>
> The other thing I once mentioned is including the docs (html/png/...) in
> the tarball or as a separate tarball along with the releases - as does
> xerces-c (they include them in the relase src tarball). Any plans about
> this ? As you already build them for the website it should be easy to
> just make a tarball out of them or include them ?
>
