*sigh* Three years after this was first reported, another round of server installs, and still no package.
Ondrej, There are applications that use php embed other than phc -- I need it for plphp -- php for postgresql databases.
Out of curiousity... since I'm not a package maintainer, how much extra time would maintaining a package for this really entail? Are we talking an hour or two a year? Or an extra 100 hours a year? Once you've got the PHP source code unpacked and configured for any of the other SAPIs, it only takes two or three extra commands ('./configure --enable-embed', 'make', 'make install') to actually get the embed library installed on the system. Is it that much more to package that up along with all the other SAPI packages? I'm not asking to be facetious, I'm just curious if it really is a ton of extra time to maintain an extra package like this or not.
*sigh* Three years after this was first reported, another round of server installs, and still no package.
Ondrej, There are applications that use php embed other than phc -- I need it for plphp -- php for postgresql databases.
Out of curiousity... since I'm not a package maintainer, how much extra time would maintaining a package for this really entail? Are we talking an hour or two a year? Or an extra 100 hours a year? Once you've got the PHP source code unpacked and configured for any of the other SAPIs, it only takes two or three extra commands ('./configure --enable-embed', 'make', 'make install') to actually get the embed library installed on the system. Is it that much more to package that up along with all the other SAPI packages? I'm not asking to be facetious, I'm just curious if it really is a ton of extra time to maintain an extra package like this or not.
---Lawrence