Re: installing multiple copies of macports

2010-10-22 Thread Jon Hermansen
I'm not running two MacPorts installs, but you should be able to switch between separate installations by just calling 'port' out by path, e.g.: /opt/local1/bin/port install mysql5-server /opt/local2/bin/port install apache2 Only network services will conflict when they both try to claim a port (

Re: [72655] trunk/dports/python

2010-10-22 Thread Ryan Schmidt
On Oct 22, 2010, at 10:51, and.dam...@macports.org wrote: > Revision: 72655 > http://trac.macports.org/changeset/72655 > Author: and.dam...@macports.org > Date: 2010-10-22 08:51:31 -0700 (Fri, 22 Oct 2010) > Log Message: > --- > Adding ssl module to python25, this is a backp

Re: [72571] trunk/dports/aqua/qt4-mac

2010-10-22 Thread Ryan Schmidt
On Oct 22, 2010, at 13:09, Michael Dickens wrote: > Hi Petr - qsci & almost all of the immediate qt4-mac dependents install for > me (10.6.4, x86_64 native I experience the same problem as Petr, with qscintilla and several other ports ou revbumped now failing to build. 10.6.4, x86_64, MacPorts

installing multiple copies of macports

2010-10-22 Thread Marko Käning
Section 2.3.4 (http://guide.macports.org/#installing.macports.source.multiple) of the manual explains how multiple macports installations can be created, but I cannot see a hint as to how these have to be set up in such a way that one can easily switch between these copies. I can imagine that s

Re: [72571] trunk/dports/aqua/qt4-mac

2010-10-22 Thread Michael Dickens
Hi Petr - qsci & almost all of the immediate qt4-mac dependents install for me (10.6.4, x86_64 native, MacPorts 1.9.99 from SVN latest, XCode 3.2.3). I updated all of these ports to use the new qt4 portgroup, which sets lots of location variables (for the most part) including where qmake is loc

Re: [72571] trunk/dports/aqua/qt4-mac

2010-10-22 Thread Petr Vanek
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi all, On Oct 21, 2010 (Thursday), at 9:44 PM, Michael Dickens wrote: >>> qt4-mac: >> [snip] >>> * add postgresql variants for versions 83, 84 (default), 90, and 91. >> >> Why not make postgresql90 the default? That is the latest stable version and