[MacPorts] #33335: Pallet doesn't work (nothing happens); no documentation

[MacPorts]

#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 dluke@…):

 Replying to [comment:2 macports_nospam@…]:
 > Just for fun, I just now tried "port list active". Viola! Just what I
 wanted -- the "port list installed" without the duplicates

 it's probably still not what you want, as you seemingly didn't read the
 FAQ you were pointed to.

 You probably want `port echo active`

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

 There's nothing /Library/Frameworks in a standard Mac installation that
 will cause problems (but you can install stuff there that might cause a
 problem. There is nothing at all in /usr/local in a standard installation
 (but again, you can install stuff there that might cause a problem).

-- 
Ticket URL: <https://trac.macports.org/ticket/33335#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS