Re: New Perl-Installation on new OS X
--As of June 8, 2011 5:39:57 PM -0400, Sherm Pendley is alleged to have said: Blaming other people for your ignorance is a habit with you, isn't it? Yes, I'm responsible for who *I* send emails to. I'm not responsible for who the list sends emails to. A correctly-configured list will look at the To: and CC: headers of any mail it receives, and won't send an additional copy to anyone who's already received one. --As for the rest, it is mine. I'd argue that's a broken list, as it doesn't send me mail with the list headers. There are major arguments over the technically correct solution. Let's not get into them here. Suffice it to say, if someone asks you to not CC them when you send to the list, it's polite not to. (At least for that discussion.) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---
Re: Need some help on installing modules...
On Sun, January 16, 2011 5:29 pm, Levan, Jerry wrote: Is doing a: sudo perl -MCPAN -e shell The standard way of preparing to install modules? Seems like root might only be needed for actual installation... Current versions of CPAN can be configured to request a sudo password at the install step, while running the rest with normal permissions. IIRC (I use cpanp, and I haven't had to set this up in a while): o conf make_install_make_command 'sudo make' o conf mbuild_install_build_command 'sudo ./Build' o conf commit In the CPAN shell should set it up for you. Depending on what order you've done things in, some temp folders may have been created with root-only access at this point, which you might need to change. (That is: If they were created by a 'sudo' run, they'll have root-only access. Otherwise they'll have access for your user.) You also don't need to go to the shell, and 'cpan' should be installed as a stand-alone script: cpan i Module::Name But all of that is basically just making things a bit less verbose and noisy. (And the one safety of not running tests as root. Note that some module tests will _fail_ if run as root...) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---
Re: Sudden death of PDF::API2
--As of February 15, 2009 11:10:33 AM +, Alan Fry is alleged to have said: I have an Intel MacPro running Mac OS X 10.5.6 (Perl 5.8.8) and a copy of PDF::API2. This has worked flawlessly for a long time. Suddenly it has failed. There have been no changes at all to the machine apart from a recent 'Security Update', which I think had to do mostly with a loophole in Safari. --As for the rest, it is mine. From the notes on the recent Security Update: perl CVE-ID: CVE-2008-1927 Available for: Mac OS X v10.4.11, Mac OS X Server v10.4.11, Mac OS X v10.5.6, Mac OS X Server v10.5.6 Impact: Using regular expressions containing UTF-8 characters may lead to an unexpected application termination or arbitrary code execution Description: A memory corruption issue exists in the handling of certain UTF-8 characters in regular expressions. Parsing maliciously crafted regular expressions may lead to an unexpected application termination or arbitrary code execution. This update addresses the issue by performing additional validation of regular expressions. So, they definitely updated Perl. Likely any/all XS modules will need to be recompiled. I'd _hope_ that Apple updated the ones they shipped, but you'll still have to update any you've installed yourself. (I haven't gotten around to installing the update myself yet...) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---
Re: Mac::Carbon, 5.10, and Leopard
--As of February 20, 2008 8:25:45 AM -0800, Tom Wyant is alleged to have said: I was able to compile, though there were test errors. I'm _not_ using File::HomeDir, so I can't comment on that part of the problem. I am using the process functionality successfully, though. $ perl -v This is perl, v5.10.0 built for darwin-2level --As for the rest, it is mine. Compiles, fails tests for me on: This is perl, v5.10.0 built for darwin-thread-multi-64int-ld-2level It looks like it's failing scripting/event tests. More specifically, it's failing to load the scripting handlers. IIRC, these were greatly restructured for 10.5, so the code probably needs to be fixed. Just as data: the tests ran to conclusion with no problems other than the errors. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---
Re: Leopard Perl version...
--As of October 14, 2007 12:26:50 PM +0200, [EMAIL PROTECTED] is alleged to have said: Why is that? Does Apple not provide the resources to make this possible? Personally I think they should because the Mac is a great development platform. I think Apple would win more developers to the platform if it were more open and a bit more up-to-date. Not shipping Apache 2 seems obstinate to me. --As for the rest, it is mine. Stability within a release version is a good goal. You never want things to _stop_ working when you put out a patch. If a developer wants the latest version of something they can put it on themselves. (Especially if it is open source.) If they are relying on the version that is installed for some reason, you don't want to surprise them by changing it unexpectedly. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---
Re: Perl OpenGL 0.55 - Need Mac testers
--As of April 19, 2007 8:46:13 PM -0400, Sherm Pendley is alleged to have said: On Apr 19, 2007, at 7:45 PM, Sherm Pendley wrote: I'm not sure why the patch to the MANIFEST file was rejected, it just adds a single line. It won't cause test failures, but the 'utils/Makefile.macosx' file won't be included in the distribution tarball without it. :-( Okay, I got that sorted - I think it was an encoding and/or line ending issue. I piped the first diff to BBEdit, then saved it; I redirected this one straight to a file instead, and it applies cleanly. sherm-- Web Hosting by West Virginians, for West Virginians: http://wv-www.net Cocoa programming in Perl: http://camelbones.sourceforge.net --As for the rest, it is mine. Works here. Mac Pro, 2.66x2 Intel, ATI Radeon X1900. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---
Re: Interacting with other applications
--As of March 24, 2007 3:31:56 PM -0500, Ken Williams is alleged to have said: Consider what happens if I'm busily typing away, and the dialogue box pops up and grabs focus, and then whatever its default is gets selected because i hit space or enter. That's exactly what a couple applications do on my machine (Backup.app and a shareware reminder for SideTrack), and I agree it's annoying. A better behavior would probably be a bouncing dock icon that defaults to yes after 30 seconds or whatever. Still annoying, but it wouldn't actually cause problems. --As for the rest, it is mine. How about calling Growl? You can have it call you back on click or timeout... http://growl.info/documentation/developer/ Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---
Re: Sendkeys
--As of Tuesday, August 30, 2005 9:14 AM -0400, macosx@perl.org is alleged to have said: I'm leaving the rest of the answers; I can check if Acrobat is scriptable when I get home though. --As for the rest, it is mine. Well, I said I'd answer this when I got home. I've got Acrobat 6 Pro, so there may be more features in the newer version. Acrobat itself is not AppleScriptable (other than using the UI scripting capability). However, it does have an automation center, where you can specify full job flows using any option you can normally use. (Look under 'Advanced' for 'Batch Processing'.) This should be enough to do your job. Also, Distiller, which comes with the pro version, *is* AppleScriptable, and can do most basic conversions for you. I don't see an option to do what you need in my version, but it may be worth looking. It may also be worth checking if Automator can do anything; it can't with mine, but version 6 came out before Automator did. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---
Re: Crypt::IDEA problems
--As of Wednesday, June 15, 2005 7:40 PM -0500, Ken Williams is alleged to have said: Don't worry, Apple has solved the Endian problem once and for all with the move to Intel: --As for the rest, it is mine. And if you believe that, I've got some nice land for you in the jungles of Venus. ;) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---
Re: CamelBones on Intel? Maybe not.
--As of Wednesday, June 8, 2005 9:02 AM +1000, John Horner is alleged to have said: My main question about the change to Intel is why the developer pack, whatever it was, costs so much? What do you get for your $999? I was expecting something free to download to developer members. --As for the rest, it is mine. As others have said, they throw in a computer. However, you *can* download the latest version of XCode and it can compile fat binaries, if I recall correctly. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---
Re: Double-Clickable or Droplet Files?
--As of Saturday, July 17, 2004 8:03 PM +1000, John Horner is alleged to have said: I was very impressed by Pashua, which allowed me to add an OS X interface to a Perl script. But I still have to call the script from the command line. Are there ways to create double-clickable or droplet-style applications in OS X, the way I used to in MacPerl on 9? --As for the rest, it is mine. One way would be to wrap them in a simple AppleScript wrapper. A few lines would do it. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---
Re: Converting PDF to JPEG
--As of Saturday, May 15, 2004 8:35 AM -0700, Rich Morin is alleged to have said: I suspect that there are Cocoa frameworks that would let me import PDF and export JPEG, but I'd rather not go that way if I can help it. Question: What's the simplest way to solve this (ie, mechanically convert PDF files to JPEG (or GIF or ...) format? --As for the rest, it is mine. If you are using Panther, you can use Apple's 'sips' commandline program to do this. It is seriously under-documented, but it works well. (Though it doesn't handle transparencies. Not a problem if you are converting to JPEG, which doesn't support them.) I've successfully used this line in a Perl script to convert images: `sips -s format $ext $imagefile --out $imagedir 21` where $ext is the extension of the file type you want to convert to, $imagefile is the name of the file to be converted, and $imagedir is the directory or output image name. The only documentation available is from the commandline: type 'sips -h' for usage help and 'sips -H' for lists of properties that are supported. Daniel T. Staal (Note: if anyone wants to help *me* use the Cocoa frameworks to do this, I would be grateful. I need to be able to convert tiff/jpeg/gif/pdf/pict/png to a common file format (png or gif), preserving transparency and color balance. So far I've not had luck on Mac. I think I could convert pure Cocoa code to Perl...) --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---
Re: [slightlyOT] reading logs with long urls
--As of Monday, May 3, 2004 4:16 PM -0400, Ken Williams is alleged to have said: How about configuring Apache to disregard (and not log) any URL longer than a predefined length? Also, what are those long url attacks, I haven't heard of them. --As for the rest, it is mine. I'll have to look into that 'disregard and not log' setup, sounds like it could be fun... A long url attack is just a buffer overflow attack. The attacker (or, more commonly, the attacker's bot) sends a request for some huge length that some webservers can't handle, with the end set to some specific binary data, which is supposed to go straight into memory (since the vulnerable webservers just keep writing past their url buffer). Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---
