Ryan Schmidt wrote:
> On second thought, I don't see why we want to install MacPorts using
> MacPorts. Doesn't that make it impossible to install MacPorts if you
> do not already have MacPorts?
No, I think MacPorts would need to do some bootstrapping on install.
But it would make commands lik
walts wrote:
> I'm trying to get a perl script that I downloaded from a source outside of
> MacPorts, and I need help resolving dependencies. For example, the script
> has
>
> use Compress::Zlib;
$ port install p5-compress-zlib
Ports for perl modules follow a simple naming scheme, just replace
Marco Battistella wrote:
> ok.
> i installed MacPort 1.6.0 in top of the old installation but while
> the old ports are still installed (good) the new macports
> installation doesn't recognize them as it's own.
> Is there a way to "tric" the new installation into recognizing the
> ports curre
I'm trying to get a perl script that I downloaded from a source outside of
MacPorts, and I need help resolving dependencies. For example, the script
has
use Compress::Zlib;
Using spotlight I found zlib buried deeply within MacPorts, but only the
folder zlib (lower case "z") containing a Portfil
