Somewhat along the same lines as ww. I might add, that given you'll likely be compiling it with your system' "package" management system. It's likely a safe bet. Given that you're system will automagically deal with any dependencies/version conflicts.
In short; just do it. :)
--Chris
Yes. What say about me, is true.
| [reply] |
| [reply] |
Maybe TITS (Try It To See)? | [reply] |
Hi,
I tried several months ago and it did not work out. I'm not exactly sure what benefits 2.4 has, but at least in my case, I see no reason to go to it. 2.2 is still being maintained, security holes are still being fixed, syntax of the conf files do not change, and mod_perl works with it.
In Ubuntu, in the default repositories, I think they are staying with the 2.2 branch, probably because of the aforementioned reasons. The syntax of the configuration files are really frustrating, because the results seem to be exactly the same. You just have to spend a couple hours learning how to make it behave in the exact same way that you already had it working, so hey, I mean, it's just your time, why copy over the old version when you can spend several hours reading documentation that you will forget in two weeks..
I mean, appreciate free awesome software though. shrug
| [reply] |
don't be afraid to complain about free software even if you appreciate it (or don't), but make it mean something other than "waah choice"
| [reply] |
Don't complain about the way I complain
Recap:
2.4 breaks compatibility in several important ways
2.4 mod_perl does not work
2.4 you have to spend time learning the new configuration syntax
2.2 Easy to upgrade
2.2 Mod_perl works
2.2 Still maintained, so no problems there
2.2 #winning
| [reply] |
See also :
http://www.gossamer-threads.com/lists/engine?list=modperl&do=search_results&search_forum=forum_8&search_string=2.4&search_type=AND
libremen.com : legal cases, contracts and insurance claims management software
| [reply] |