Darren J Moffat <[EMAIL PROTECTED]> wrote:
> > Once star is in, it would be a task of minutes to integrate more from the
> > "schily enviroment".
>
> I think you are making it harder for yourself by targeting ON. Given
> that you have a known working stable build environment SFW is probably a
> better choice.
>
> The only something should be in ON are usually:
>
> 1) it exposes a private interface to other things in ON
> 2) the ON build depends its source - not binaries (ON already
> depends on binaries from SFW and other consolidations to build)
> 3) it depends on a consolidation or project private interface in ON
> and an ARC contract isn't a suitable way to coordinate because of
> the complexity of a cross consolidation flag day.
>
> Replacement of something currently in ON isn't necessarily a reason.
> For example replacement of tar by star doesn't imply that start needs to
> be in ON just because tar was (unless one or more of the above also apply).
With this description, several files would need to go to ON that currently are
not. libm is such a candidate...
If you believe that star should go elsewhere, then somebody from Sun would just
need to create a wrapper makefile.
In any case, the integration of cdrtools would need to be overhouled because
all schily software is developed in a unified environment.
If people like to use the libraries from the schily environment, the include
files from the schily portability environment need to be installed into
/usr/include/schily/* and the libraries need to be made available for other
software.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
opensolaris-discuss mailing list
[email protected]
