Please review first draft of Fossick - a MacPorts GUI

[Ian Wadham]

On 21/04/2013, at 11:49 AM, Ryan Schmidt wrote:

> On Apr 20, 2013, at 20:09, Ian Wadham wrote:
> 
>> 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.

In Fossick file SoftwareProviders.m, around about line 80, there is code to set up nested
NSDictionary data for MacPorts, as a software provider.  In the future, it should be possible
to configure this better using the info you have provided below, especially in Fossick's
advanced mode.

For now, you could work around this problem (and see more of Fossick) by inserting a line:

    inputFile = @"/Users/rschmidt/macports/dports/PortIndex";

in Fossick file (Providers) MacPorts.m, just before the line that begins with "NSLog(@"===> START:".

> 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.

Thanks, Ryan.  I will take this info on board, for use in later development of Fossick.

Cheers. Ian W.