On Jan 25, 2008 10:04 PM, Jyri Virkki <Jyri.Virkki at sun.com> wrote: > Henry Jen wrote: > > > > Uh, sorry for the confusion. I may have too many wrong assumptions > > regarding what is delivered into Nevada. Pointers for some > > clarification would be much appreciate. > > Apache (w/APR) is in SFW consolidation. > > To provide APR as an independent package the change is only to tweak > the build to make it into an independent package (or packages) and > then have apache & svn depend on it. (A lot of paperwork and a good > amount of testing will accompany that, so it'd actually take a long > time to do, but the changes should be fairly small.) >
That is a way to approach it, and you are suggesting to use apr and aprutil source bundled with apache httpd source. Personally I prefer to follow the apr/apr-util tree directly as they are different projects, although the releases are pretty close, they are still separately projects. Like I said, I found there are SFE spec files for those two libraries already, and I think we should not waste time to duplicate efforts. As the package approach, I found myself prefer pkgbuild approach over SFW approach, simply because pkgbuild is more close to what upstream provides, ie, not to separately maintain files include in a package most of time. > As to APR depending on sqlite3, is that in nevada today? As of which > build? Unless you need a consolidation-private dependency on it, it > shouldn't matter if it's coming from a different consolidation. > > The spec file is in JDS repo, but is not in nv80, not sure when will it be included. I don't know what do you mean by consolidation-private dependency(I need to get educated on Consolidations and Solaris development process). What I care is that sqlite3 to be there for both build and runtime. Cheers, Henry
