Please review first draft of Fossick - a MacPorts GUI

[Ryan Schmidt]

On Apr 20, 2013, at 20:09, Ian Wadham wrote:

> On 21/04/2013, at 9:43 AM, Ryan Schmidt wrote:
> 
>> On Apr 20, 2013, at 18:17, Ian Wadham wrote:
>>> On 21/04/2013, at 7:33 AM, Ryan Schmidt wrote:
>>>> All three panes are empty; I can't figure out how to make it do anything.
>>> 
>>> I am sorry to hear that.
>>> 
>>> It probably means it has crashed somehow during launch.  Does the Console
>>> app say anything useful?  What Xcode and OS X versions did you use?  Fossick
>>> should start by listing all the ports, starting at 2Pong, and then become responsive.
>> 
>> Yes, the Console says some things; I'm attaching the output.
>> 
>> <fossick.txt.bz2>
>> 
>> It's Xcode 4.6.2 on OS X 10.8.3.
> 
> Thanks, Ryan.  That's very strange.  Everything worked OK, except for a couple of
> (OS X 10.8?) grumbles I don't see on Lion.  Fossick gets its list of ports (ATM) from
> the MacPorts Index file, but finds no ports on your system.  It also runs commands
> "installed", "requested" and "outdated" internally, to get statuses, and it finds some ports …
> 
> Fossick is looking for the "port" command in /opt/local/bin and the Index file in
> /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/PortIndex.
> 
> Do you perchance have your MacPorts Index file in a different place?  Is there
> a smarter way to locate that file?  I hate using literals in programs.

That explains it. My primary PortIndex is in /Users/rschmidt/macports/dports/PortIndex.

Consult /opt/local/etc/macports/sources.conf to see where users have their ports tree(s). The default sources.conf lists:

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

Mine contains:

file:///Users/rschmidt/macports/dports [default]

Note that users can specify multiple locations, each of which will contain a PortIndex and which MacPorts will use simultaneously, with ports encountered in later PortIndexes overriding those found in earlier ones or in the default group. For example, if a user didn't like the standard zlib port, they could put their own zlib port in their own directory, run `portindex` on it, include it in sources.conf after the default, and it would effectively "hide" the official port. Or this feature can be used to gain access to additional ports which are not part of the official collection; perhaps a collection of private ports.