Danek, I've been reading the materials you linked me to regarding procedures. One thing that didn't seem clear, was that it wasn't specified what hardware architecture to compile it on. x86, x64, or Sparc.
Also, it seems that I need to be running a relatively recent version of Solaris Express. This raises an issue for me because my home server is an X1 running Solaris 8. (I know I know, but I don't have spare hardware to migrate it to.) Because of this I was contemplating some options for a build system(s). 1) Get an x86-64 1u cheap rack system and run Linux w/ VMware server on it. This would let me setup a x86-64 build environment in a VM. (Plus test environments as needed.) 2) Same as number one, but I create a VM running S10 to migrate my X1 apps to. This would give me Sparc hardware to build a test environment, and/or x64/86 as needed. 3) Find someone else in the community that is already maintaining a build server/servers, and use them to do the builds. 4) See if I can trick Sun into creating some public use zones for me to do my builds in. I would like to hear what people suggest.
I just realized something. I am being naive. Historically Sun has not > upreved the version of the application, but has backported "patches" into > the existing codebase. I am not sure whether or not, rebuilidng with new > source, or backporting fixes into "our" source is the correct way going > forward for this application. I'm not sure what this means. I think that if you still need to ask this question after you've looked at the build system, you should try asking it again then.
An example should illuminate what I am trying to ask. Say, I had a project to include applicationxyz version 3.4.1 in SOlaris11/nv. Say there were 3 security patches and 10 bug fixes included in two maint. releases. The new application version is 3.4.5. As a maintainer would I upgrade the OpenSolaris package to version 3.4.5 of the package, or would I manually create a 3.4.1_patched1? Thanks, Brian
_______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
