How to merge multiple user's iTunes libraries into one library (assuming their all the same iTunes User account)

Note these directions are for a Mac (but would only need slight modifications to work on a pc)
(These haven't been fully tested yet, please let me know if you find issues)

So you're a family of 6 and you each have a login on the same mac:

1. Dad
2. Mom
3. Son1
4. Son2
5. Daughter1

First you need to decide which user will "own" the master library. So if we select "Dad", then Dad should log into the mac.

1. Login to the user whose library you'll be working on 
2. Launch iTunes
3. Select iTunes -> Preferences (Or hit Splat-,)
4. Click on the Advanced tab  (Make a note of the "iTunes Media folder location")
5. Select "Keep iTunes Media folder organized"
6. Select "Copy files to iTunes Media folder when adding to library" 
7. Click "OK" and close the preferences folder
8. Select File->Library->Organize Library (This will copy all files into the directory specified in the advanced user preferences tab as the base directory, and organize them according to the wisdom of iTunes)
9. At this point all Dad's music files should be organized.
10. Repeat 1->7 for the rest of the users (Mom, Son1, Son2, Daughter1)
11. Make a note of the location of the iTunes library for each user when you're in the advanced tab.
12. Now log back into the Dad's account
13. Start iTunes
14. Click on File->Add to Library...
15. Select the directory for the user's library you're consolidating into this library.
16. Click OK
17. Repeat 12->16 for the rest of the users you're consolidating into this library

And.. You're done.

One thing this won't do is migrate playlists into the master account.

How to configure bugzilla to use perl from somewhere besides /usr/bin

Whenever I install bugzilla I always build a separate perl tree just for it's use.

I do that for the following reasons:

1. I don't like to alter the system install perl by building packages into it
2. By having a separate perl install, I can be ensured that no one adding packages or altering the perl install will break my bugzilla install
3. If I build my perl and bugzilla into a someone portable file system (such as /opt/bugzilla ), then I can tar up the install and install via untarring on another system (assuming same os version and architecture)

Here's the code to swap out the perl location in the scripts from the bugzilla FAQ

perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl contrib/*pl

How to build php 5.3.2 and apache 2.2.x on RHEL4

I had fun with this, so I figured I'd post it for others.. :)

Unpack apache and configure:

tar xvfj httpd-2.2.15.tar.bz2
cd httpd-2.2.15


./configure --prefix=/opt/local/webroot --enable-so

make
make install
cd ..

 Unpack php
tar xvfj php-5.3.2.tar.bz2
cd php-5.3.2
( Note: if you aren't on 64bit platform, you can likely skip the  --with-zlib-dir and --with-libdir arguments)
./configure  --prefix=/opt/local/webroot --with-apxs2=/opt/local/webroot/bin/apxs --with-config-file-path=/opt/local/webroot/php --with-mysql=/usr/include/mysql --with-zlib-dir=/usr/lib64 --with-libdir=lib64 --with-ldap --with-ldap-sasl
make
make test
make install

And you can follow This

Pragmatic Version Control Using Git by Travis Swicegood Review

Having worked in configuration management for the last 15 years or so, I've been exposed to most of the mainstream version control systems.  Recently I've been using BuildBot and found an fixed some bugs. They use the git revision control system (hosted on github), so it was time to learn something new.

So thanks to Tony,  Baypiggies' publisher interface, I was able to obtain a review copy.  So now just find the time. :)

I've read both the CVS and Subversion editions of Pragmatic version control from The Pragmatic Programmers and in both cases found the books well written and easy to read.

As Git (The version control system originally written by Linus when the bitkeeper folks decided the cancel the license they'd granted to Linux) is one of a new generation of Distributed Revision Control systems, it's necessary to take a step back from what you may already know about revision control.  Git tracks diff's and not files.

The first chapter does an admirable job helping one wrap one's head around the fundamental differences between Git and the centralized repository based RCS's.

The second chapter walks through obtaining and setting up Git on your favorite platform(s) (Linux, Mac OSX, and Win-blech OS's are discussed)

The third chapter has the reader create a repository, and then walks you through a number of checkins and basic command usage.  That ends the first section.

The second section (composed of 6 chapters) walks you through increasingly complicated examples with a fictitious project.

Finally, the third section is composed of two chapters on administrative topics, migrating to Git, and running a git server.

As I expected, this book upholds the high standards set by the CVS and Subversion editions of this book, and is a great introductory read to get anyone up and running with Git!