RPM's are insanely easy to create, and the work helps with deployment/version tracking on the end machine. For example I have an .spec that downloads a given version of codeIgniter, unzips it, tweaks some permissions, and then rolls it into an RPM and tosses it into a network accessible repo. The RPM has a pretty complete list of dependencies, so they automatically get pulled in.
So my devel script looks something like:
cat <<EOF
"EOF" > /etc/yum.repos.d/local-repo.repo
[local-repo]
name=local-repo
baseurl=http://xxxx
enabled=1
gpgcheck=...
EOF
PACKAGES="codeigniter otherstuff"
for PKG in $PACKAGES; do
sudo yum install -y $PKG;
done
RPM's are insanely easy to create, and the work helps with deployment/version tracking on the end machine. For example I have an .spec that downloads a given version of codeIgniter, unzips it, tweaks some permissions, and then rolls it into an RPM and tosses it into a network accessible repo. The RPM has a pretty complete list of dependencies, so they automatically get pulled in.
So my devel script looks something like: