Print Story Please tell me there is a better way...
Spent literally three non-stop days with the site down.  Turns out Rose::DB needed weak references, which wasn't supported in the version of perl that is installed by Susu 9.1  Fuckers.  Well, actually I'm the fucker.  I knew that running different OS versions on dev & production would equal pain eventually.

...  the answer is version control.  The question is how.



I spent the week re-compiling every little library used the system.  When done on an old ass computer, this process takes 15->45 minutes per library.  Once done, I checked in the compilied binary into my repository.

I've never worked on large-scale system where this stuff becomes critical.  What do you check in?  How do you handle paths?  How do you handle the various and sundry architechtures in use?

Basically, how do you do it?  I know I'm part there.  Everything is now under config management.  All the libraries are smeared into a single /vendor/bin/libs kind of deal.  Is there a better way?  Is there any kind of open sauce tools that ride on top of subversion that do this stuff for me?  Is there any low-cost closed sauce tools?

Full discussion: http://www.hulver.com/scoop/story/2006/6/25/143150/720