[EMAIL PROTECTED] wrote: > > Known issue. Solaris has the strict rule that we're not allowed to ship > > any *.so files if the API is not public, therefore we do not ship the > > *.so files. However some people may be interested to play around with > > the API (e.g. to build ksh93 plugins (builtin commands, functions etc.)) > > ... the *.so links can easily be restored by hand but the lint files > > cannot be "restored" if we don't ship it. That's why we're ending up > > with a weired chimera shipped with three legs where leg No. 4 can be > > substituted with a wooden one on demand (erm... Ok... this metapher > > isn't a good one... ;-( ). > > I'm confused. If these APIs are not public, then people should not be > playing around with using the APIs except in the context by which > they're ARCed. If they're Project Private, then only the ksh93 project > inside the ON consolidation may use them.
What about "contracts" between individual projects, e.g. dtksh vs. ksh93 in OS/Net or dbx vs. ksh93 in OS/Net ? Would that be a justification to ship the lint libraries (I guess the answer is "no") ? Alternatively we could create something like a "SUNWastprivateplayground" (e.g. "AST private API playground") package which provides the private API add-ones as a seperate package stored at the project website... ... would it be allowed to have the package build pieces for such a thing in usr/src/pgkdefs/ (e.g. we built the package but do not ship it with Solaris nor ARC it (for now)) ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
