On Jul 30, 2011, at 20:36, james collins wrote:

> On Jul 30, 2011, at 8:30 PM, Ryan Schmidt wrote:
> 
>> The MacPorts disk image installer does install MacPorts into /opt/local; 
>> there is no option for it to do anything else.
> 
> I see the folder for macports in /opt/local/etc
> 
> But no folder in /opt/local
> 
> And then there is files in like /opt/local/var etc.
> 
> That is why I say macports is in /opt/local/etc

/opt/local *is* the MacPorts folder. Yes, it contains folders like etc, var, 
share, lib, include, bin, and so on, and those folders contain subfolders, and 
some of them are named "macports", and so on. This is normal.


> And I am getting another error regarding xapian-core
> 
> And I can't find xapian-core on my computer?
> 
> Should macports have installed it?

MacPorts should have made the xapian-core port recipe, and all other port 
recipes, available to you, by virtue of running "sudo port selfupdate", but 
apparently your selfupdate is having trouble, for a reason that we have not yet 
been able to figure out.

You are sure /opt/local/etc/macports/sources.conf has not been modified? It 
should contain several comments (lines beginning with "#") and then the 
following line:


rsync://rsync.macports.org/release/tarballs/ports.tar [default]


If that's not what's in it, put that in it, then try to selfupdate again.

If that is what's in it, is there perhaps a problem connecting to rsync servers 
from your network? If so, you'll have to tell MacPorts to use some other method 
to get the ports collection, for example http, documented here:

https://trac.macports.org/wiki/howto/PortTreeTarball

or svn, documented here:

https://trac.macports.org/wiki/howto/SyncingWithSVN

Then try to selfupdate again.


_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Reply via email to