multiple-versions

I had the PHP, MySQL, and Apache stack installed for development. That installation is using configuration files from: /etc/apache2/ /etc/php5/ Later I installed multiple PHP version using phpbrew . All versions are accessible and switchable from CLI. But Apache always stays on the default version that was not installed using phpbrew . Here is a list of my installed PHP versions. $ phpbrew list Installed versions: php-5.4.13 (/home/admin1/.phpbrew/php/php-5.4.13) +default -- --with-bz2=/usr php-5.5.5 (/home/admin1/.phpbrew/php/php-5.5.5) php-5.3.27 (/home/admin1/.phpbrew/php/php-5.3.27) I have

I want to install, from source, Perl versions 5.005 , v5.6 , v5.8 , v5.10 Right now I have 'v5.10.0' installed. /opt/perl/bin /opt/perl/html /opt/perl/lib /opt/perl/man /opt/perl/lib/5.10.0 /opt/perl/lib/site_perl /opt/perl/lib/site_perl/5.10.0 Will I have any problems if I install them all in /opt/perl ? Or should I split them up into their own, version specific, directories? Like /opt/perl-5.10.0/ I install all of my perls completely in their own directory so they don't share anything with any other perl. To do that, you just tell the Configure script where to install everything. I like /usr

I'm wondering if there's any way to tell pip, specifically in a requirements file, to install a package with both a minimum version ( pip install package>=0.2 ) and a maximum version which should never be installed (theoretical api: pip install package<0.3 ). I ask because I am using a third party library that's in active development. I'd like my pip requirements file to specify that it should always install the most recent minor release of the 0.5.x branch, but I don't want pip to ever try to install any newer major versions (like 0.6.x) since the API is different. This is important because

How would I go about installing 2 versions of jQuery using bower ? I want to have v2.0 as well as 1.9.1 for browser support fallback The issue I'm having is that if you run bower install jquery#1.9.1 jquery#2.0.0 the first version gets overwritten by the second because they are the same component In the dependencies part of your bower.json you can have something like this: "dependencies": { "jquery": "2.0.0", "jquery-1.9.1": "http://code.jquery.com/jquery-1.9.1.js" } One shouldn't normally have to do this, but sometimes you have to maintain / migrate an existing website that (for whatever

I'm working with a third-party assembly and unfortunately I now need to load their latest and a previous version into my project so at runtime I can decide which one to load. I only ever need one, not both. With this in mind, I am also dependent upon the types provided by the components so I cannot load from reflection and query every time for the method/events/interfaces that I want to use. I have seen some mention of handling this via AppDomain s but am not sure how to proceed. Would the process be to code against one version of the component and then at run-time (using the AppDomain ) swap

I have the following situation Project A - Uses Castle Windsor v2.2 - Uses Project B via WindsorContainer Project B - Uses NHibernate - Uses Castle Windsor v2.1 In the bin folder of Project A I have the dll Castle.DynamicProxy2.dll v2.2 and NHibernate dlls. Now the problem is that NHibernate is dependent on Castle.DynamicProxy2.dll v2.1 which is not there. How do I resolve this situation. I used the following configuration to resolve the issue. <configuration> <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Castle.DynamicProxy2"