till wrote:
Even though this will go off-topic - but hey f' that! :D
Well getting PHP installed, running, and maintained is sort of relevant to developing and running RoundCube :)
[snip]
So what happens is, it "unloads" all extensions (including PCRE) and wants to use PCRE, and dies. Of course the work around is to use ports to install the PECL module as well - but yeah, we are all human and make mistakes.
Ahh... that must be why I haven't had this problem. I use ports for everything.
IMO this should be also fixed by the maintainer - I have not heard of a work around to include PCRE without hacking the Makefile, or maybe using CONFIGURE_ARGS.
It should probably do like perl and some others do, when CPAN or what-have-you installs a module, it does register it with the ports system. I did have trouble with some PEAR modules I installed by hand once that never got listed anywhere, but the modules I needed have since been added to the ports system so I had forgotten about that.
Ruby has a similar issue with gems. I know some gems, like those for rails, have their own ports but they often lag way behind and it's easier to use gem to keep them up to date on your own.
It would be nice to have a Makefile option or an alternate meta-port that would build with some or all extensions static. It might even be in progress. I'd check the ports mailing list archive and the GNATS system to see if someone has opened a PR about it.
I just don't like having to remember that to include it accross updates. That kind of defeats the purpose for me, but of course that is all doable. I could also roll my own port - not too hard, but yeah
- I actually just want to "consume". ;-)
Same here. It must just be luck that has let us get by with the minimal trouble we've had. "It Works For Me"(TM) -- most of the time. :)
I also have a patch for my pecl issue, but somehow I doubt they accept my "workaround".
Well it wouldn't hurt to mail it to the ports list or file a PR. The worst that can happen is it gets closed or ignored. If enough people chime in, the maintainer or a developer may take notice and propose a better fix or adopt yours.
The OpenSSL issues I found were related to some weird warning/failure PHP issues when I connected to a payment processors SSL endpoint. I was told on bugs.php.net that my install "sucks" because it's build shared and not static, when everyone in the world knows it has to be static. Well too bad. ;-)
We don't use SSL in PHP for anything mission-critical. (Our billing system runs in Perl.) In fact, I think the only place we use it is in RoundCube for the spell-checking functions if they're routed through Google. Again, probably luck that's spared us from that trouble...
I don't want to bash anyone, so I guess php should offer guidelines for the distributions and collaborate with maintainers on those issues. (In a perfect world.)
That would be nice. I'd love to see a mechanism for the ports system to respect the order of my extensions and how they load. I know others have the problem, they even linked to my writeup when talking about it on several different mailing list posts. I guess nobody has been able to come up with a workable solution yet (myself included...)
Jim
List info: http://lists.roundcube.net/dev/