Mike Kupfer wrote: > > >>>>> "Roland" == Roland Mainz <roland.mainz at nrubsig.org> writes: > > Roland> Offtopic: Will this include the full history of changes in > Roland> Solaris, too ? > > We can't provide full histories for all files.
Why ? > But IIRC the plan (at > least for ON) is to provide the SCCS delta comments for the 5 years > prior to the June 2005 launch. That's close to Solaris 7 FCS, right ? [snip] > >> 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. > > Roland> The idea of using a branch at genunix.org was to create a > Roland> prototype for development, testing and evaluation. > > Hmm. I'm a little concerned about this possible scenario: a bunch of > work is done to get everything working with genunix.org[1], then a > relatively small amount of development work happens--enough to meet the > minimal requirements for integration into ON--, then April integrates > ksh93 into the OpenSolaris source base. At that point, there would be > three different source bases (the OpenSolaris one, the genunix one, and > the AT&T one). Seems like it could get messy. Erm... actually my idea was to work on the prototype at genunix.org in a branch based on a more or less stable version of OpenSolaris (e.g. builds+boots on both x86 and SPARC without problems). Once the prototype has been finished&&approved the work gets moved to the OpenSolaris repository within Sun. At this point the branch at genunix.org will be abadoned so we only have to deal with two versions: Sources in OpenSolaris and the official AT&T distribution. > On the other hand, I like the idea of a project with both internal and > external committers. And I can see where making the commit mail > available would be a good thing, as you say. The idea is actully coming from OpenSource projects such as Mozilla.org or X.org/Xfree86 where this is the standard to keep everyone informed. > *shrug* It's not clear to me what the right approach is. April, do you > have any thoughts on this? > > Roland> for now I would be glad to get some actual work done and get > Roland> ksh93+libshell.so integrated into OpenSolaris > Roland> - and then decide the next steps... ... and maybe add libast to that list, too - see my other email about perl being a canidate for using libast's sfio code - assuming this results in a performance boost... > Notes: > [1] I've seen a few internal email messages from people trying to use > SVN through Sun's firewall. The mails pretty uniformly say it's > painful, apparently due to problems with Sun's network infrastructure > and proxies. Known problem. You may want to try to use "svn" build with SOCKS support (e.g. configure --with-socks= at build time). And there are java-based socks server available which are pretty much secure and crash-proof (thanks to java) which could be placed at some SWAN gateway... > One of the messages did say something about it being > easier with https, but I'm hazy on the details. Only if the https traffic isn't filtered itself (sounds weired - but some firewall products do really horrible things even with so-called "secure" transports... ;-( ). ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;)
