[MacPorts] #33335: Pallet doesn't work (nothing happens); no documentation
MacPorts
noreply at macports.org
Fri Feb 24 10:09:24 PST 2012
#33335: Pallet doesn't work (nothing happens); no documentation
--------------------------------------------+-------------------------------
Reporter: macports_nospam@… | Owner: juanger@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.0.3
Keywords: | Port: Pallet
--------------------------------------------+-------------------------------
Comment(by macports_nospam@…):
> "port list" [wiki:FAQ#portlist does not do what you think it does].
As always, "port list" shows EVERY port, installed or not. What I needed
was a list of INSTALLED and ACTIVE ports, without all the duplicates that
come up with "port list installed." As noted in the wiki:FAQ, the
preferred syntax is "port installed," but that produces ALMOST the same
list as "port list installed." ("port installed" shows you which ports are
active; "port list installed" displays the category of each port instead.
As an experiment, I ran both commands. Each produced a 327-line output.
When I manually pasted the output into an editor and removed the
duplicates, that dropped to 187 lines. Nearly half!
Just for fun, I just now tried "port list active". Viola! Just what I
wanted -- the "port list installed" without the duplicates
> Having frameworks installed in /Library/Frameworks, or libraries
installed
>in /usr/local/lib, causes problems for many ports; it is not feasible to
> separately for each port include a message reminding the user of that
fact.
Frankly, that's just short of snide. OF COURSE you should document if a
particular port has a conflict with something in a standard Mac
installation. Duh. AND... are there any side effects from stripping out
pieces of the standard Mac OS, outdated or not?
--
Ticket URL: <https://trac.macports.org/ticket/33335#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list