This discussion is archived
3208 Views 6 Replies Latest reply: Mar 16, 2010 11:45 PM by dbernelle
Currently Being ModeratedSep 27, 2009 12:44 AM (in response to loopkin)Hi,
I figured to install wxPerl. Had to compile Perl, wxWidgets etc. I described the whole idea here:
http://ecocode.net/article.shtml?092009.txt-001MacBookPro 2.66Ghz, Mac OS X (10.6.1)
Currently Being ModeratedFeb 3, 2010 12:23 PM (in response to loopkin)Can anyone provide me with a status on when this will be fixed by Apple for 10.6.x?
...or are Mac OS 10.6 users left to their own "fixes" to circumvent the breakage in code for Perl?
I have one utility that uses Perl and this breakage in code directly effects this utility such that it no longer works.
The reason I have stayed on 10.4.x and delayed in upgrading to 10.5 and later, on to 10.6 is this very break in Perl functionality.
- DaleMacPro 2 x 2.66 GHz Dual-Core Intel Xeon, Mac OS X (10.4.11)
Currently Being ModeratedFeb 3, 2010 8:15 PM (in response to dbernelle)We are just users like yourself.
I would encourage you to file a bug with Apple at either:<http://www.apple.com/feedback/macosx.html>
Free ADC (Apple Developer Connection) account needed for BugReporterMacBook, iMac/i7, PowerMac/G5, Mac mini, iBook/G4, MacBook Pro, iMac/G4, Mac OS X (10.5.8), iPod Touch
Currently Being ModeratedMar 16, 2010 11:45 PM (in response to BobHarris)Thanks!
I did both of what you suggested (and provided very detailed specifics of the wxPerl broken code) and was told:
1st Case (Feedback): No response to my feedback
2nd Case (ADC bug report): No response after obtaining an ADC account and filing a bug report
Next, I wrote a letter to Apple, addressed to the "Macintosh Software Development Manager," providing details of the wxPerl broken code problem, the "Problem Details and System Configuration" error log from one of the many failures while trying to launch the TivoTool 0.7.0 application, remarked on the length of time that this wxPerl code has been broken (broken in 10.5.x & 10.6.x software releases) and detailing how this is disabling the TivoTool application and any other user that is dependent on wxPerl functioning. I asked that a trouble report be opened, the problem resolved, and the fix be made part of a software update. Additionally, I requested an estimated date for this resolution to be included in a software update.
I also sent a copy of this letter and enclosures, along with a cover letter, respectively addressed to Mr. Steve Jobs, asking that he provide the proper resources to clear this long time defective code.
Within a couple of weeks (on March 5, 2010) I received a telephone call from an Apple Executive Contact (named "Nate"), due to the letter addressed to Mr. Jobs. After gathering details on the broken wxPerl code, he promised to contact the software development folks and get back to me with his findings. Within a week of this initial contact, he again telephoned (on March 9, 2010) to say that he had contacted the software development folks, provided the information from my broken wxPerl report, that a trouble ticket was opened on the wxPerl broken code problem, and that the wxPerl broken code problem appeared to be a "low runner," e.g. not many users had reported the wxPerl broken code. Additionally, since the broken code was a "low runner," there was no target date to fix the wxPerl broken functionality.
He suggested, until the wxPerl broken functionality was resolved, that I might want to keep a 10.4.x System hard drive available, so that when I needed the wxPerl functionality, I could boot my Mac under 10.4.x, perform my wxPerl work (e.g. use TivoTool), and then re-boot again later, under 10.6.x to use the TivoTool obtained files.
He also suggested that I make sure that the Software Update System Preference be enabled to automatically check for updates ("Scheduled Check" tab). He added that I shouldn't rule out that the wxPerl broken code functionality might one day be resolved through a Software Update.
I was given a case number, for future reference and to allow me to check the status of my wxPerl broken functionality trouble report.
As my dad used to say, "That's all she wrote."
So, because this is a "low runner" (e.g. not many people have noticed and reported the broken wxPerl code), I'd be surprised (but very delighted) to see a wxPerl fix delivered by Apple in the near future. After all, wxPerl has been broken since leaving Mac OS 10.4.x (wxPerl broken in 10.5.x and 10.6.x software releases).
I last spoke to Nate regarding this issue on Mach 9, 2010.
I have not included Nate's telephone number out of a courtesy to Nate, as he is not a technical person, only a contact that handles issues which have been escalated to Apple executives.
The Apple Case Number assigned was: 153683921
Regards to all involved and all effected.
- DaleMacPro 2 x 2.66 GHz Dual-Core Intel Xeon, Mac OS X (10.6.2)