Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Some of my BackPAN stuff is pulling out bits of PAUSE to index things. Ultimately I want my BackPAN work to do the same job as PAUSE but for a different purpose: make index files for whatever people want to do. (But PAUSE also does all the user management stuff too).

    Besides that, I'd eventually like to get a shadow PAUSE running just so there's an extra one lying around ready-to-go.

    And, once I do that, I should be able to branch the code and see if there are ways that we can uncouple parts of it. Since we'll have shadow PAUSE running the mainline code, we should be able to do regression testing pretty easily.

    If you're interested in pulling out more stuff on PAUSE, maybe we should organize a bit of a hack-a-thon for it. Maybe not in person, but we pick out a feature to see if we can abstract it. Once we do that, maybe we can slowly roll things back into PAUSE. I've looked at the code too, and I think I know how it works, but it's not something that easy to uncouple.

    • That was precisely my impression: not easy to uncouple. Having a second copy of PAUSE running for our hacking pleasure and potentially as a fallback would be great.

      I'd be all for hacking on this together, but you're right: Having a development copy of PAUSE would be indispensable.

      • I did some ugly things [] which run the actual mldistwatch code using some monkeypatches and a mock DBI object, etc. Mostly it is a matter of emulating the environment. Perhaps the code could be refactored to make this easier (so you don't need all the uglies.)

        And wouldn't it be cool if the mock DBI object could actually be a frontend to query the actual PAUSE via a web service?! Then you could know what is really going to happen if you upload your code right now, etc.

        • Or how about having the data in a couple of SQLite files locally for testing?