Shawn Walker writes: > On Dec 28, 2007 11:16 AM, Coy Hile <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > I don't know if this is the appropriate venue to ask this question, but I > > can't find a build-specific mailing list. What is the appropriate > > procedure to check out and build the SysV packages for just a subset of the > > WOS? Specifically, I'm looking to grab the sources for SUNWssh* and build > > just all of that. I've got a multi-platform environment, and I was going > > to see if I can get SUNSSH to build on other platforms rather than having > > SunSSH on all my solaris boxes and having OpenSSH-some-version on the > > others to avoid any interoperability/config problems, etc. > > > > It all depends on what consolidation the program is delivered by. > > For example, if SUNWssh was part of ON, you can't just rebuild that > portion of it into a package currently.
That's almost true. There's no 1-to-1 mapping of source directories to packages in ON. Some source directories build objects used by multiple packages, and some packages deliver things built in multiple different directories. So, you need to know what you're packaging and how the source is organized. In general, you should be able to go to $SRC and type "make sgs", then go to the source directory of interest (say, $SRC/cmd/ssh), type "make install", and then go to the packaging directory ($SRC/pkgdefs/SUNWsshu) and "make install" there to create the package. That's only "in general," though. Many packages will be different, and you'll need to read the source. If you *aren't* intimately familiar with how that given project is integrated into ON, then I certainly wouldn't suggest attempting this. It's almost certain to lead directly to misery. Use "nightly". This is exactly what it's for. As for any interoperability problems, I run multiple versions of ssh myself, and certainly haven't seen any such issues. We have support for many different standards-based protocols ... why would ssh be a special exception? And why not report those things as bugs rather than try to work around them by creating a monoculture? -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
