> Date: Wed, 6 Dec 2006 13:48:46 -0800
> From: Danek Duvall <danek.duvall at sun.com>
> To: April Chin <April.Chin at eng.sun.com>
> Cc: gk at onnv.eng.sun.com, roland.mainz at nrubsig.org,
ksh93-integration-discuss at opensolaris.org
> Subject: Re: proposed solution for LD_LIBRARY_PATH problem
> Mime-Version: 1.0
> Content-Disposition: inline
> User-Agent: mutt-ng/devel-r535 (SunOS)
>
> On Wed, Dec 06, 2006 at 01:32:33PM -0800, April Chin wrote:
>
> > So we may want to ARC the addition of libpp/msgcpp/msgcc now. Roland
> > Mainz has been advocating this, and I'm beginning to see now that this
> > makes sense.
>
> Does to me, too.
>
> > So would it be reasonable to use a wrapper script to the message-building
> > portion of the ksh93 build, with LD_LIBRARY_PATH pointing to a $TMPDIR
> > containing links to the proto area as a temporary solution? This wrapper
> > script could be removed after maybe 3 or 4 builds (whatever seems
> > appropriate), with an accompanying flag day.
>
> Given that the messages won't be translated until we start approaching FCS,
> can we simply postpone the message build for a couple of builds? The
> targets can all be in place and usable for anyone who wants to (and can)
> build them, but the .po files would need to not be in SUNW0on.
>
> Will ksh93 be in its own self-contained package that can easily be added to
> a build machine on receipt of the flag-day message?
>
Integrating initially without the message building would be fine for us.
No, ksh93 is not self-contained in its own package...its changes
affect several packages, including SUNWarc, SUNWcsu, SUNWcsl.
Thanks,
April
> Danek
