[Sorry for the cross-post, but this discussion involves several projects] A quick context on what is the goal:
To make libapr-1 and libaprutil-1 available on Neveda. Apache, svn depends on those libraries, so is JXTA-C. JXTA-C also requires libaprutil-1 to be built with apr_dbd_sqlite3 support, meaning, sqlite3 needs to be available before build libaprutil-1. Sqlite3 is now in JDS spec-file repository. When I am adding libapr-1 into sfwnv, I found libapr-1 and libaprutil-1 are in the SFW extra-spec-files repository[1]. With that, I think we should coordinate the effort to move apr and aprutil from SFW into SUNW, but I am not sure how different consolidation works together to deliver packages in common interest. Maybe the F/OSS project is the right place? Cheers, Henry [1] http://pkgbuild.svn.sourceforge.net/viewvc/pkgbuild/spec-files-extra/trunk/ On Jan 24, 2008 5:38 PM, Henry Jen <henryjen at ztune.net> wrote: > I took a look at the build process for sfwnv, thanks Jyri for the > pointers, this should be relative easy. Let's discuss how to get this > going. > > First of all, we will need to determine the package name, seems like > with Solaris convention, binary and header files are delivered in one > single package instead of like Debian/Ubuntu which would have > binary/devel packages, thus I would like to propose: > > 1. SUNWlibapr-1 : The binary and header files for libapr 1.x. > 2. SUNWlibapu-1: The binary and header files for libaprutil 1.x > > The latest version is 1.2.12 and can be downloaded from > http://apr.apache.org/download.cgi > > As JXTA-C project, we will need apr_dbd with sqlite3 driver built, > thus will add dependency to sqlite3, there was a discussion on include > sqlite3 into Solaris, but I am not sure which consolidation is taking > care of that. Anyone knows? > > Cheers, > Henry > > > > On Dec 2, 2007 9:39 PM, Henry Jen <henryjen at ztune.net> wrote: > > On Dec 2, 2007 7:27 PM, Jyri Virkki <Jyri.Virkki at sun.com> wrote: > > > Peter Tribble wrote: > > > > > > > > > > I got a quick question, are we delivering libapr and libaprutil as > > > > > > separate packages or as a whole in the apache? > > > > > > > > > > > For Apache 2.2.6, they are delivered as part of SUNWapch22u package. > > > > > > > > Requiring an apache server being installed in order to meet library > > > > dependencies seems to me to be a bad idea. > > > > > > > > (I logged 6544042 earlier; that was for the svn case.) > > > > > > > > Would it make sense to package APR separately? > > > > > > Probably make sense if there are other clients using it [as there are]. > > > > > > > At least there are svn and httpd. :-) I really think libapr and > > libaprutil should be package separately. > > > > > As things move from the one-DVD distribution model to the a la carte > > > package selection there's going to be a lot of package refactoring > > > that needs to be done. As usual, please file bugs to track such > > > refactoring work in general (the above CR works for this particular case). > > > > > > > > > > I am not familiar with the snv/webstack build process, but I can help > > in the apr/apr-util related bug fixes to the upstream if needed. > > > > Cheers, > > Henry > > >
