I did realized that tree was a command line utility, that was why I wanted it.
After installing it, tree was still not working from command line. At some later time, it magically started working. Perhaps I had quit Terminal and restarted at some point, I don’t recall. Shouldn’t the install process ensure the utility is in working state or does a person always have to quit terminal and restart, or perhaps open a new Terminal window? What is the accepted procedure? What is the best macports gui front end? > port contents tree results in: Port tree contains: /opt/local/bin/tree /opt/local/share/doc/tree/CHANGES /opt/local/share/doc/tree/LICENSE /opt/local/share/doc/tree/README /opt/local/share/man/man1/tree.1.gz Thx Ken On Apr 23, 2014, at 12:16, Arno Hautala <[email protected]> wrote: > On Wed, Apr 23, 2014 at 1:27 PM, Ken G. Brown <[email protected]> wrote: >> >> Now that tree apparently is installed, how do I run it, where is the >> executable? > > The executable is probably installed at /opt/local/bin/tree > You can check for sure using "port contents tree" > >> Is there something I am missing in setting up to be able to run the MacPorts >> installed programs? > > I'm guessing that you didn't realize that "tree" is a command line > utility, as is most of the software provided by MacPorts, though there > are some graphical wares. > > "tree" and the "port" command that I listed above can be run from > Terminal.app. > > -- > arno s hautala /-| [email protected] > > pgp b2c9d448 _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
