- group=$(echo $group_plus | sed -e "s,+++, ,g")
- yum -c ${vdir}/etc/mkfedora-yum.conf --installroot=${vdir} -y groupinstall "$group"
+ yum_group=$(echo $group_plus | sed -e "s,+++, ,g")
+ echo " * yum groupinstalling $yum_group"
+ yum -c ${vdir}/etc/mkfedora-yum.conf --installroot=${vdir} -y groupinstall "$yum_group" || \
+ echo " * WARNING image $systemslice - yum groupinstall $yum_group failed"
+ done
+
+ # running pip or gem requires connectivity, and DNS
+ # so we expose the build-vm's /etc/resolv.conf to the current vdir
+ mkdir -p ${vdir}/etc
+ cp /etc/resolv.conf ${vdir}/etc
+
+ # this requires pip to be available in sliceimage at that point
+ # fedora and debian -> python-pip
+ # on fedora the command is called pip-python (sigh.)
+ for pip in $systempips; do
+ echo " * pip installing $pip"
+ chroot ${vdir} pip -v install $pip || chroot ${vdir} pip-python -v $pip || \
+ echo " * WARNING image $systemslice - pip install $pip failed"
+ done
+
+ # same for gems; comes with ruby in fedora but ruby-devel is most likely a good thing
+ # we add --no-rdoc --no-ri to keep it low
+ for gem in $systemgems; do
+ echo " * gem installing $gem"
+ chroot ${vdir} gem install --no-rdoc --no-ri $gem || \
+ echo " * WARNING image $systemslice - gem install $gem failed"