On 8/3/05, Justin Patrin <papercrane@gmail.com> wrote:
I'm trying e17 as well after reading this ;-)
Great Justin :)
I suggest emerging edge before epsilon or you'll get compile errors.
I just finish compiling it and I got no problems (at least that I'm aware of)... so it also works with this sequence :)
I found this script which uses portage to update E17, but checks if
packages were modified since last update. When the first package is
found, that one and the remaining (onwards) are emerged. This seems to
save a time compiling unmodified packages!
Also found other scripts to compile directly from cvs, without using portage. Can anyone tell me what the advantage of doing so?
Christoph, is there so many modifications to update E17 every day? What about once a week?
the script:
#!/bin/bash
CONTINUE=1
####### This is not a complete list of e17 packages!! #####
E_LIST="eet\
edb\
evas\
ecore\
embryo\
edje\
epeg\
epsilon\
esmart\
engrave\
ewl\
e\
e_utils\
engage\
e_modules"
echo -ne " \033[01;33m *\033[01;00;0m Do you want to run rsync to backup current cvs? [Enter/Yes or No]: ";
read REPLY;
case $REPLY in
"" | [yY]*)
rsync --progress --delete -ab /usr/portage/distfiles/cvs-src/e17 /mnt/backups;
;;
*)
echo -e " \033[01;33m *\033[01;00;0m Continuing to emerge";
;;
esac
for i in $E_LIST
do
echo -e " \033[01;33m *\033[01;00;0m Updating $i cvs";
if [[ $CONTINUE -eq 1 ]]; then
E_PATH=`equery which $i`;
UPDATE=`ebuild $E_PATH unpack | grep -e "^[UP]"`;
echo $UPDATE;
ebuild $E_PATH clean;
if [ ! -z "$UPDATE" ]; then
CONTINUE=0;
echo -e " \033[01;33m *\033[01;00;0m Waiting 10 sec
before continuing with emerge from this package onwards... package =
$i";
echo -ne " \033[01;31m *\033[01;00;0m "
for j in $( seq 1 10 )
do
echo -ne "\033[01;31m$(( 11-j ))\033[01;00;0m ";
sleep 1;
done
echo " ";
fi
fi
[[ $CONTINUE -eq 0 ]] && emerge --oneshot $i;
# [[ $CONTINUE -eq 0 ]] && echo -e " \033[01;33m *\033[01;00;0m emerge --oneshot $i";
done
Cheers,
Fernando