>>>>> "Roland" == Roland Mainz <roland.mainz at nrubsig.org> writes:

Roland> - Would Sun like/dislike the diversion between OpenSolaris
Roland>   vs. Solaris in this point ? AFAIK SchillyX and other
Roland>   distributions did already expore this part (e.g. ksh93
Roland>   residing at /usr/bin/ksh) quite successfully

Currently, the ON part of OpenSolaris is mechanically generated from
Solaris.  At some point this will be flipped around, so that OpenSolaris
contains the "master" workspace.  Either way, any divergence has to be
coded into the makefiles, using a switch to determine whether ksh means
ksh88 or ksh93.

I don't think anyone in Sun would be happy with such a divergence.  I'll
ask if folks would accept it, temporarily, but I'd also like to explore
alternatives.

One alternative would be to manually change /usr/bin/ksh to mean ksh93.
You'd have to redo this any time you installed new Solaris Express bits.
But building and BFUing OpenSolaris would leave /usr/bin/ksh alone.

Roland> Cyril Plisko <cyril.plisko at gmail.com> from genunix.org said we
Roland> could have a branch in their SVN (=Subversion) respository -
Roland> which may be ideal for getting a prototype running.  

We should also have Subversion support on opensolaris.org "soon".  But
if the team wants to use Subversion, I guess using genunix.org would
help things get started more quickly.

The alternative would be for April to deliver snapshots as tarballs;
external contributions would come back as source patches.

Of course, Subversion would be easier for collaborative development than
tarballs and source patches.

Roland, IIRC, you mentioned some interest in helping with development
work, but you also have concerns about whether Sun would integrate ksh93
and then say there's nothing else to do.  I know *I* can't make any
guarantees about what happens after ksh93 is added to the source base,
and I'm not sure what guarantees April can make, if any.

What I'm trying get at is that if there are external folks who are
likely to contribute code, then it makes sense to consider using
genunix.org for the development work.  But if April is going to do all
the development work, it might be simpler to use the tarball approach.

cheers,
mike

Reply via email to