In 12 hours I leave for the Oslo QA Hackathon. Right now I'm copying all 10 Gb of BackPAN to a portable USB drive and a thumb drive. It's taking a long time. While I waited I created a Google Map for the things I need to find in Oslo (such as my hotel).
April 2 is the Oslo.pm meeting. I get into town about eight hours before that, so here's hoping that I can stay awake for it. When I went to Oslo for NPW 2006, I ended up staying up all night because nobody told me they don't turn off the sun during the summer. There I am thinking it's about dinner time and it's 1 am. I should have an easier time with the QA Hackathon because the sun actually sets. It looks like it will be nice Chicago weather too.
Now that it's Oslo time, I can start thinking about the stuff I want to do at the hackathon. Part of my task is indexing BackPAN. Besides finding modules in distributions, I also want to find packages, I think. By convention, we normally make a package per file and give it the same names, but it doesn't have to be that way. So how to find the package names given a file? I could just match the text, but I think I want to try using PPI to look for real package declarations. It's a bit easier than the normal problem since package has a bareword following it. I won't mess with those in eval. That's a nice little project for the plane ride.
Jonas from Copenhagen tells me he might come out for the weekend, and since he's training for a marathon and I'm working toward a half-marathon, I also need to go running when I get there so he doesn't kill me on a Sunday long run. That's okay. I get in at about noon and I don't get to check in to the hotel until 3. I need something to pass the time anyway. :)
Won't this get in the way of this common trick?
package # hide from PAUSERe:PPI'ing package
Alias on 2008-04-01T12:03:35
No, it won't get in the way in the least.
PPI reads code like people do, so if YOU can see that it should be hidden, PPI is quite capable of emulating the stupidity of PAUSE.:)
