Our beloved cpan command line has some tricks up his sleave. In case you haven't read the fine CPAN manual in a while, let me point out some features I'm using right now to install all the needed modules for my day-to-day operation. cpan . You have a local directory with a module already unpacked, or your own personal module. The usual way to install them is doing the dance:
Just a quick word pointing out that perl 5.10 was released the 18th, 20 years after the first perl release. As Grubber says, Perl is the best language in the world. At least to both of us. The 5.10 release adds a lot of improvements to Perl over the 5.8.x series. I would recommend that you take the time to read through perl5100delta, it should take less than an hour, but its definitively worth it.
... a 18 months old kid with a death wish. My youngest soon though that my iPod 5G was thirsty, so he offered it a bottle of water. The iPod was stupid enough to accept it, and now, not only I'm out of a Macbook Pro, I'm also iPod-less. Merry Christmas to me! PS: anybody going the the US soon? I have a order for you!
If you upgrade SSHKeychain to 0.8.2, and start seeing Buggy password in keycahin workaround in Console.app (btw, it really is spelled keycahin in the source :) ), then go into Keychain Access and remove all SSHKeychain entries. Problem solved.
While my Macbook is in the shop, I "borrowed" my sisters Mac Mini G4. Oh, G4, how much I loathe you... Let me count the ways: cd ~/src/some_software && time make Update: for future reference - starting a Catalyst app I'm working on, it takes 17 seconds. Previous Macbook Pro: 2.
With three quick releases, Fluid has been getting a lot of attention. Given that it is Leopard only, I haven't tried it yet, but looking at the feature list, it doesn't seem to offer much more than Prism, Mozilla Labs version of the same concept (on which Fluid was inspired). The best update so far was 0.3 adding auto-updates via Sparkle. My take on Prism and Fluid, is that they don't go far enough.
So I need to decide what to do with my broken 17" laptop. I'll try and see how much would it cost to fix this, but replacing a LCD is always the most expensive operation. If I have to buy something new, I'll probably won't buy a Macbook Pro again. I spend a lot of time in the office now a days, so I can work on the road with a smaller laptop.
Ok, time to panic. My laptop LCD is going bonkers. A ruined laptop is something I do not need now. Update: yep, I'm severely fsck'ed. The lower half of the LCD on my 17" Macbook Pro is berserk. Running with external LCD for now, while I decide what to do. Happy Christmas to me. Update 2: Left the laptop at the most recommended Authorized Apple support shop. Hope to hear from them today.
Talk about targeted advertising... (via Worse than Failure)
In RFC: Dropping namespaces: I still have not heard any good reason why namespaces in the current implementation are actually useful - or what particular case they solve... so I am wondering, are they really useful? I come now to the conclusion that they are not, and for myself (and most likely my work projects) I would have to decide not to go with namespaces, but instead stick with the 3 letter prefixing.