I've not written this yet, tyr "update_e17.sh --help"
There
are two basic ways it will fail. The first is the script will fail
during the source download phase. If it fails then, remove the offending library
file from the easy_e17.sh. Mind you it will be listed in two places
so use the search function to find them.
The second place the
script is likely
for fail is during the build process. At which case it's not the
scripts fault, but operator error. Some dependency
is missing. The error message will tell what is missing ( the tmp/log
file will also list what happened ). Apt-get what is missing and
restart the easy_e17. script with "easy_e17.sh -i -s", this
will skip re-downloading the source
files and will pick-up from where it failed.
Their is a third
likely
(very likely)
way in which the script fails, it os neither the fault of the
easy_e17.sh script or operator error, but rather that the eDevelopers
are mucking 'bout with some source code. There is not much one can do
in this case other then to wait. Aye, one can delve into the failed
log file and see if they can sort out the problem.
Or one can go to the Enlightenment
Forum looking for a solution (good luck with that). I have
found that simply waitting till there is a new version is the
quickest & easiest
thing to do. Just re-run the easy_e17.sh (with just the -i flag) and
when it updates the library that failed
to build source you should be good to go (or maybe not if the
eDevelopers are in a particular
feisty
mode).