On Wed, 18 Jun 2008 17:15:18 +0530 Seema Alevoor <Seema.Alevoor at Sun.COM> wrote:
> Hi, > > One of the tasks planned for webstack Apache is the decoupling of > APR, APR-UTIL from HTTPD and introducing them as separate packages. > This is required as many other components actually depend only on > APR/APR-UTIL libraries and do not require HTTPD libraries. > > Now that Apache 2.2.9 has been released with APR/APR-UTIL 1.3, it is > the ideal time to work on this task (CR 6715153, CR 6714814). > > It could be done > 1. using the apr, apr-util bundled with httpd source but built > binaries moved to a separate pacakge. > 2. using apr and apr-util sources (with the support for multiple > versions), built and packaged separately. > > In my opinion 2nd one is the better option. It gives us more control > over packaging and version updates. Yep, option 2 is clearly best. Then in future we can update APR/APU and HTTPD as separate packages. > We can have the following type of packages: > 1. package containing only the libraries > 2. dev package which contains mainly the header files ( needed for > development ) 3. APR-UTIL database driver packages That makes sense to me. I haven't checked where we are on this, but with APR-UTIL, we're planning more modularisation. In particular, it should be possible to separate out LDAP in the same manner as the DBD drivers in the near future, if not already. The basic idea (upstream) is to separate out those parts of APR-UTIL that add bloat by linking in extra libraries. Database and LDAP drivers are the main cases, but other modules could follow. -- Nick Kew
