Update pallet port to new version

[ultrajoe@…]

When I try to launch Pallet.app under OS X 10.4.11 (PowerPC), it brings up the initial window, asks for the admin password, thinks for about 30 seconds (whirling the throbber), then crashes. I cannot get it to do anything.

I have tried uninstalling & reinstalling without success.

The .dmg someone else posted will not run on my system.

I've attached a build log (sudo port -v install Pallet) and the crash report.

[ultrajoe@…]

Build log of Pallet + MacPorts_Framework (output of sudo port -v install Pallet)

[ultrajoe@…]

Crash report

[jmroot (Joshua Root)]

Yeah, the current version in the ports tree is known to be kind of broken. See MacPortsGUI for the new improved version. I'll leave this open as a request to update the version in the ports tree.

[blb@…]

Note that the new version requires at least 10.5.

[ultrajoe@…]

Either MacPortsGUI needs to be backward compatible with Tiger, or Pallet needs to be the Tiger interface and needs to be fixed.

Perhaps it's time I learn to develop OS X apps?

[jogonzales@…]

is there anything that works with 10.4? cause even Porticus reports that it is damaged and needs repair. ATM no gui will run on 10.4

I get the same crash report

[nerdling (Jeremy Lavergne)]

People should be trying to move off of 10.4 soon …

[ultrajoe@…]

Replying to snc@…:

People should be trying to move off of 10.4 soon …

Several classic (pun intended) problems with this line of thinking:

1. Older hardware that isn't supported by the Leopard family ("warm" and Snow) are still in use. I'm sure donations of/for newer hardware would be accepted, though, especially a top-of-the-line 8 CPU Mac Pro... :)
2. Tiger is the last to support the Classic environment (see the pun now?), which some of us still use.
3. MacPorts still comes in a Tiger flavor.

So, sorry, this argument doesn't hold much water.

[blb@…]

Replying to ultrajoe@…:

1. Older hardware that isn't supported by the Leopard family ("warm" and Snow) are still in use. I'm sure donations of/for newer hardware would be accepted, though, especially a top-of-the-line 8 CPU Mac Pro... :)

Many PowerPC should be able to use 10.5 as well...

1. Tiger is the last to support the Classic environment (see the pun now?), which some of us still use.

True, this is one cause; though you could also keep a small 10.4 partition around for classic use only, otherwise use 10.5.

1. MacPorts still comes in a Tiger flavor.

For now, though the official policy is to support the current shipping OS version and one previous, which technically means 10.4 is not on the list anymore.

[ultrajoe@…]

Replying to blb@…:

Replying to ultrajoe@…:

1. Older hardware that isn't supported by the Leopard family ("warm" and Snow) are still in use. I'm sure donations of/for newer hardware would be accepted, though, especially a top-of-the-line 8 CPU Mac Pro... :)

Many PowerPC should be able to use 10.5 as well...

But not all.

2. Tiger is the last to support the Classic environment (see the pun now?), which some of us still use.

True, this is one cause; though you could also keep a small 10.4 partition around for classic use only, otherwise use 10.5.

For that matter, have a 9.2.2 partition/drive for such an occasion.

3. MacPorts still comes in a Tiger flavor.

For now, though the official policy is to support the current shipping OS version and one previous, which technically means 10.4 is not on the list anymore.

(sigh) Fine, then. I'll consider myself desupported, as always, because I'm financially unable to upgrade my hardware to your specifications. (Sorry, but I get so sick of this argument.)

[blb@…]

Replying to ultrajoe@…:

(sigh) Fine, then. I'll consider myself desupported, as always, because I'm financially unable to upgrade my hardware to your specifications. (Sorry, but I get so sick of this argument.)

Note that MacPorts itself (from the command line) still supports 10.4, it's simply pallet that requires 10.5+.

Also, you may get sick of it, but this is an all-volunteer open source project which has very limited resources and can't easily support everyone's system. We have to make decisions on what to support and how, so we could either decide to drop older systems because we don't have the people to otherwise support it, or to try and do at best a half-assed job and spread ourselves even thinner than we already are. The latter helps nobody.

[ultrajoe@…]

Very well. I guess someone can mark this as "fixed" or "submitted by an idiot" or whatever you wish. Meanwhile I'll deinstall MacPorts.

[ultrajoe@…]

Sorry, should've said "deinstall Pallet" not MacPorts. (It's been a BAD day.)

[domiman@…]

Since this topic seems to be the one that gets pointed at when someone reports problems with Pallet (regardless of OS X flavor - see ​http://trac.macports.org/ticket/21467), I'd like to add that neiter Pallet from the ports nor the MacPortsGui run without crashing on SL 10.6.1. When choosing the TCL location the MacPortsGui Pallet will crash all the time. If you need more information, please tell me which. I didn't dare to post my own bug report after seeing the reply to #21467.

[blb@…]

Replying to domiman@…:

Since this topic seems to be the one that gets pointed at when someone reports problems with Pallet (regardless of OS X flavor - see ​http://trac.macports.org/ticket/21467), I'd like to add that neiter Pallet from the ports nor the MacPortsGui run without crashing on SL 10.6.1. When choosing the TCL location the MacPortsGui Pallet will crash all the time. If you need more information, please tell me which. I didn't dare to post my own bug report after seeing the reply to #21467.

Pallet's issue (from the DMG) on 10.6.1 is most likely due to having only a MacPorts 64bit set of libraries, but Pallet is 32bit (PowerPC and Intel) only; for that issue I've opened #21837, since this ticket's purpose really should be just updating the port of pallet to be more current.

[domiman@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Replying to jmr@…:

I'll leave this open as a request to update the version in the ports tree.

Is there something blocking updating this port?

[juanger@…]

The Portfile has been updated to use the latest source.