[ksh93-integration-discuss] Re: Re: [osol-code] ksh93-integration prototype004 2007-01-27 webref+diff

[James Carlson]

Richard L. Hamilton writes:
> However, I think it might not be unreasonable if they were made available separately
> (as a plain tar file on the project page) _outside_ the tree, so that anyone wanting to
> play (with the full understanding that nothing they did would be accepted until the
> interfaces were no longer project private) could get a headstart.
> 
> That way, if someone wants to start independent work on reconciling a less reduced
> set of builtins with the non-builtin versions, they could do that based on the (once
> it happens) integrated ksh93 rather than on their own separate build of it, which would
> increase the odds of their having something acceptable and/or simplify the merge work
> they'd have to do if and when the interfaces were made more than project private.
> 
> Is that a workable compromise?

It works for me; there are no architectural or consolidation rules
about what you deliver in your own tarballs.

It can even be in a package that's built but not delivered to the WOS
(similar to SUNWwbint or SUNWzoneint), if that works out better for
the team.

A simpler answer is to make SUNWastdev this package, though I suspect
that'd result in yet more controversy.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677