[MacPorts] #33335: Pallet doesn't work (nothing happens); no documentation
#33335: Pallet doesn't work (nothing happens); no documentation --------------------------------------------+------------------------------- Reporter: macports_nospam@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: --------------------------------------------+------------------------------- I successfully compiled Pallet after having to track down and resolve the /Library/Frameworks//Tcl.framework problem (i.e., the need to delete this directory before MacPorts_Framework would compile). It loads fine and lists a bunch of ports. Clicking on one port to Upgrade it just moves the port name to the attached drawer. Nothing else happens.There's no Help. Right-clicking does nothing. (System: 2006 MacPro, 10.6.8 Snow Leopard) Some documentation would be nice. You should mention the need to delete the Tcl.framework before installing on the MacPortsGUI wiki page. Is there a way to list both installed and all available ports? (The terminal command "port list installed" fills the terminal with lots of duplicates.) -- Ticket URL: <https://trac.macports.org/ticket/33335> MacPorts <http://www.macports.org/> Ports system for Mac OS
#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 --------------------------------------------+------------------------------- Changes (by ryandesign@…): * owner: macports-tickets@… => juanger@… * port: => Pallet Comment: "port list" [wiki:FAQ#portlist does not do what you think it does]. 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. -- Ticket URL: <https://trac.macports.org/ticket/33335#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#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
#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
#33335: Pallet doesn't work (nothing happens); no documentation --------------------------------------------+------------------------------- Reporter: macports_nospam@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: Pallet --------------------------------------------+------------------------------- Changes (by ryandesign@…): * owner: juanger@… => macports-tickets@… Comment: juanger has retired. -- Ticket URL: <https://trac.macports.org/ticket/33335#comment:> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts