Jyri Virkki wrote: > Sriram Natarajan wrote: > >> Hi >> modules like suphp (http://www.suphp.org) is unable to compile out of >> the box because of the way we deliver apr/apr-util. Is there any >> > > How/why exactly? > > What it it relying on? Packaging details don't alter the bits that > ultimately end up on disk once all relevant packages have been > installed. So unless suphp is checking the package database, how > would it know? > > >> particular reason, why we cannot deliver these files in the same fashion >> as done on other platforms ? >> > > It's a common pkg split, same as on other platforms (debian, Ubuntu). >
FWIW, APR-Util won't be separately distributed as of APR 2.0, but instead will be part of APR proper. > >> Do we expect apr component to have multiple >> binary incompatible releases ? >> > > IIRC that was discussed in the case, but don't remember details > offhand. Check the ARC case. > > Binary incompatible releases won't collide, even if all installed to the same prefix. The bin directory would have apr-config (0.9), apr-1-config (1.x), and apr-2-config (future 2.x). There would be separate build, build-1, and build-2 directories, separate include/apr, include/apr-1, and include/apr-2 directories, and so forth. Libraries are versioned as well. Related: ARC cases generally (?) have considered the open source package interfaces uncommitted.
