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

use Perl Log In

Log In

[ Create a new account ]

domm (4030)

  (email not shown publicly)

Just in case you like to know, I'm currently full-time father of 2 kids, half-time Perl hacker, sort-of DJ, bicyclist, no longer dreadlocked and 33 years old

I'm also head of [], maintainer of the CPANTS [] project, member of the TPF Grants Commitee [] and the YAPC Europe Foundation [].

I've got stuff on CPAN [], held various talks [] and organised YAPC::Europe 2007 in Vienna [].

Journal of domm (4030)

Saturday January 12, 2008
06:09 AM

Hacking on hardware, CPANTS and git

[ #35372 ]

CPANTS things first: I finally managed to grab some time for a long-needed CPANTS revivication. I switched back to postgres (SQLite was just too slow for the huge amount of data (and/or I was to dumb to set the tables/indeces/sql correctly)), I installed everything on the new server (big thanks to maks for showing me how get Debian to be able to actually compile stuff (apt-get install build-essentials) (I'm a bit spoiled by two years of gentoo usage :-)), and after surprisingly little time, everything basically worked.

I still need to fiddle with Apache/mod_perl, and check if automatic updating actually works, but in the meantime you could check out this: (which is running under the Cat dev server, so don't expect very high performance...). Oh, and some links are broken (eg 'dist/Acme' should be 'dist/overview/Acme')

I also had to hack some hardware yesterday - well, acutally it was more like drilling hardware. I finally bought a new snowboard (Burton), but my rather old Flow binding had it's holes in the wrong place. So I drilled them myself (in the binding, not the board...).

At my new job (more infos ASAP), we decided to use git. I don't know if it's because I'm getting old (I'm starting a new bit soon) or because git is alien and complicated, but it took us several days to work through the docs and approximatly 10 test repos until we understood the general workflow and how to implement it.

And finally, this graphic made sense, even if you add a small amount of branches and tags

                      you push
your personal repo ------------------> your public repo
      ^                                     |
      |                                     |
      | you pull                            | they pull
      |                                     |
      |                                     |
      |               they push             V
their public repo <------------------- their repo ries

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.
  • Many of the key Git developers hang out on #git. You might have saved a bit of your 10 days by asking a few questions there.
    • Randal L. Schwartz
    • Stonehenge
    • We did (not me but my colleague koki). And it didn't took us 10 days... But thanks for the tip.