| View previous topic :: View next topic |
| Author |
Message |
bob_111
Apprentice
Joined: 12 Oct 2004
Posts: 155
|
 Posted: Wed Aug 03, 2005 2:04 pm Post subject: E17 scripts |
 |
|
Hey guys, ive been using E17 for about 6 months now and have made some shell scripts. I peffer not to use portage for CVS stuff so here they are!.
e17updatecvs.sh
| Code: | #/bin/sh
export WANT_AUTOMAKE=1.7
export WANT_AUTOCONF=2.5
build=" e17/libs/imlib2
e17/libs/edb
e17/libs/eet
e17/libs/evas
e17/libs/ecore
e17/libs/epeg
e17/libs/epsilon
e17/libs/embryo
e17/libs/edje
e17/libs/esmart
e17/libs/etox
e17/libs/ewl
e17/libs/emotion
e17/apps/entrance
e17/apps/e
e17/apps/eclair
e17/apps/e_utils
e17/apps/e_modules
misc/engage
misc/erss"
cd $HOME/CVS_E17
cvs -d:pserver:anonymous@cvs.sf.net:/cvsroot/enlightenment login
cvs -z3 -d:pserver:anonymous@cvs.sf.net:/cvsroot/enlightenment co $build
|
e17compilecvs.sh
| Code: | #/bin/sh
export WANT_AUTOMAKE=1.7
export WANT_AUTOCONF=2.5
build=" e17/libs/eet
e17/libs/edb
e17/libs/evas
e17/libs/ecore
e17/libs/embryo
e17/libs/imlib2
e17/libs/edje
e17/libs/epeg
e17/libs/epsilon
e17/libs/esmart
e17/libs/emotion
e17/libs/ewl
e17/apps/entrance
e17/apps/e
e17/apps/e_utils
e17/apps/e_modules
e17/apps/eclair
misc/engage"
for i in $build
do
clear
echo "##### COMPILING ${i} #####"
cd $HOME/CVS_E17/$i
./autogen.sh --prefix=/usr/local
make uninstall
make
echo "##### INSTALLING ${i} #####"
make install
done
|
e17compilesingle.sh
| Code: | #/bin/sh
export WANT_AUTOMAKE=1.7
export WANT_AUTOCONF=2.5
clear
echo "##### COMPILING ${1} #####"
cd $HOME/CVS_E17/$1
./autogen.sh --prefix=/usr/local
make
echo "##### INSTALLING ${1} #####"
make install
|
Currently the update script gets all the stuff out of the E17 cvs tree iirc. It can be eaisly modifyed  . I hope this can assist some of those "i cant install e17" threads.
- bob_111 |
|
| Back to top |
|
 |
giglio
n00b
Joined: 22 Jul 2005
Posts: 24
|
| Posted: Wed Aug 03, 2005 2:19 pm Post subject: |
|
|
| Looks cool, I'll try them out tonight. |
|
| Back to top |
|
|
giglio
n00b
Joined: 22 Jul 2005
Posts: 24
|
| Posted: Wed Aug 03, 2005 9:06 pm Post subject: |
|
|
| they work great, the only change I made was add sudo before make install. |
|
| Back to top |
|
|
ppurka
Advocate
Joined: 26 Dec 2004
Posts: 3256
|
| Posted: Thu Aug 04, 2005 6:03 am Post subject: |
|
|
| Quote: | | Hey guys, ive been using E17 for about 6 months now and have made some shell scripts. I peffer not to use portage for CVS stuff so here they are!. |
Thats a bunch of nice scripts to automate the process if we don't want to use portage. Thanks!
Meanwhile, I have been using the following script, since I update my e17 through portage: | Code: | #!/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 |
What the above script does is, it checks the output of cvs for lines starting with U or P, which indicate that there is something new updated in that package. If it gets such lines, then it emerges from that package onwards. Thus, if there has been no updates in eet, edb, and evas, but a file has been modified in ecore, then the above script will emerge all the packages starting from ecore onwards. But it will not emerge eet, edb and evas since there is nothing new to compile.
Another point to note is that the E_LIST does not contain all the packages (it contains only the ones I am using  ). However, other packages can be easily included in that list, taking care of the e17 compilation order.
Hope it helps. |
|
| Back to top |
|
|
RuiP
l33t
Joined: 15 Jan 2005
Posts: 643
|
| Posted: Wed Mar 01, 2006 11:32 am Post subject: |
|
|
Hi all,
i've been posting my script on E17 is coming?? (Part 3) but here is the correct place to put it.
It's a mix of the script at Gentoo Wiki HOWTO e17, my adptation of the idea of ppurka (see above script, install/upgrade only the needing ones) and some other common routines associated with e17 updates management that i want to make it simple and with minimum typing from user.
(Please check my last note on this post)
-> Here is the latest version <-
(latest version is 0.2.1, from 03/Mar/06)
Don't forget to check and change the E_LIST to your preferences and make it executable.
Check available flags by reading it or just do: update-e17.sh -h
Here is an How-To use it:
(1.) To Install or Update
This will download and install everything need it. It will only emerge out-of-date and needed packages, if you are doing an update.
If it fails because it couldn't login, then
(1.a) you can resume an aborted install/update with forced mode (keep trying in case of failure):
in fact you can use that command to do an emerge --resume in forced mode to any other package, not only to e17 packages.
(2.) When you have a working version, backup that pearl:
(3.) Then, if future updates broke things or don't work, it just need to
do a cleaning and reput a good backuped version:
Other things:
If install or update fails (server slow days) try the alternative server,
or the forced mode (will try 30 times 'till is done it):
or you could be more specific about how many time you want to try, e.g.:
| Code: | | update-e17.sh -F 50 |
or you could specify one package from the e17 package list to start from.
e.g, on my list if i only to update modules stuff:
| Code: | | update-e17.sh -F e_modules |
will update on forced mode e_modules, embrace and engage, the 3 last packages.
Or if your update failed at evas you can go for forced mode starting from that with:
| Code: | | update-e17.sh -F evas |
Doing backups is highly recommended, here some extra useful commands:
| Code: | | update-e17.sh -b package-only |
| Code: | | update-e17.sh -b cvs-tree-only |
Check available flags:
hope you find it of usefull 
NOTE: update-e17.sh -c just apply my ususal preferences. Change it to yours...
UPDATE: I found this on Ubuntu forum and is definitly a better solution than emerge packages:
http://omicron.homeip.net/projects/easy_e17/easy_e17.sh
It compile all from cvs but everything is installed on only one directory at /opt. Thats the right place for alpha stuff. Not mixed with the system as emerge do.
You could have several installations side-by-side, named e17_26-MAR, e_17_15-MAY and so on and link the one you want to use as /opt/e17.
Isn't that cool? I have a pre-shelf and a up-to-date versions to use and work and at same time check how development is going on...
_________________
ESTRAGON: We've lost our rights?
VLADIMIR: (distinctly) We got rid of them.
Last edited by RuiP on Wed May 24, 2006 11:48 am; edited 5 times in total |
|
| Back to top |
|
|
hulmeman
Apprentice
Joined: 02 Jul 2002
Posts: 184
Location: Duchy of Lancaster, England.
|
| Posted: Fri Mar 03, 2006 4:01 pm Post subject: |
|
|
| RuiP wrote: | Hi all,
i've been posting my script on E17 is coming?? (Part 3) but here is the correct place to put it.
It's a mix of the script at Gentoo Wiki HOWTO e17, my adptation of the idea of ppurka (see above script, install/upgrade only the needing ones) and some other common routines associated with e17 updates management that i want to make it simple and with minimum typing from user.
-> Here is the latest version <-
(latest version is 0.2, from 01/Mar/06)
Don't forget to check and change the E_LIST to your preferences and make it executable.
Check available flags by reading it or just do: update-e17.sh -h
Here is an How-To use it:....................................................................... |
I'm getting a syntax error with the script so:
| Code: | # ./update-e17.sh -u
**********************************************************************
* This script is based on a script found at Gentoo Wiki HOWTO e17, *
* a script from ppurka on Gentoo Forum and other ideas from myself, *
* to make e17 install/updates management an easy task! *
* Check 'E17 is coming?? (Part 3)' thread at Gentoo Forum *
* for more information on this and Enlightenment17 in general. *
**********************************************************************
./update-e17.sh: line 208: syntax error near unexpected token `;'
./update-e17.sh: line 208: ` if [ "$2" -gt 0 ]; then; NTRYS="$2"; fi'
|
Help? |
|
| Back to top |
|
|
brian33x51
Tux's lil' helper
Joined: 16 Jun 2002
Posts: 118
|
| Posted: Fri Mar 03, 2006 4:17 pm Post subject: |
|
|
[quote="hulmeman"] | RuiP wrote: |
./update-e17.sh: line 208: syntax error near unexpected token `;'
./update-e17.sh: line 208: ` if [ "$2" -gt 0 ]; then; NTRYS="$2"; fi'
[/code]
Help? |
that should read:
if [ "$2" -gt 0 ]; then NTRYS="$2"; fi
remove the extra semi colon. |
|
| Back to top |
|
|
RuiP
l33t
Joined: 15 Jan 2005
Posts: 643
|
| Posted: Fri Mar 03, 2006 6:10 pm Post subject: |
|
|
Hi, sorry by that hulmeman.
yes, brian33x51 is right, there a killing semi-colon...
thats something i changed at last minute, just deleting lines and forgetting that one 
But i believed i had update a correct version... I must check the on-line version.
There is another bug, -R flag only update the first package of the e17 list.
I'm a little short in time, now, i'll put a solved version in a few hours.
again sorry by the inconvenience.
Rui |
|
| Back to top |
|
|
RuiP
l33t
Joined: 15 Jan 2005
Posts: 643
|
| Posted: Fri Mar 03, 2006 9:01 pm Post subject: |
|
|
OK, I think is working correctly now.
to loadder_ (next post)
I answer you on 'e17 thread'
Last edited by RuiP on Mon Jun 26, 2006 7:53 pm; edited 1 time in total |
|
| Back to top |
|
|
lodder_
Apprentice
Joined: 06 Nov 2004
Posts: 162
Location: Knokke-Heist, Belgium
|
| Posted: Mon Jun 26, 2006 1:15 pm Post subject: |
|
|
thx RuiP it's looks very good wil test it when i'm home. But i have still one questions what is the full list of programs for e17 that would be great
_________________
delodder.be |
|
| Back to top |
|
|
RuiP
l33t
Joined: 15 Jan 2005
Posts: 643
|
| Posted: Fri Jul 14, 2006 12:22 am Post subject: |
|
|
Hi,
i recently post some links on 'e17 is coming?' to a modified version of easy_e17.sh, but here is the right place for those things.
easy_e17.sh has a new version, 1.0.3, that already include same of my desired features (not download all cvs sources),
but unfortunantely just for --only flag (!?)
I made a patch to apply to that new version with some add-ons and some extras.
----------------------------
Here are the changes:
----------------------------
--date=<DATE> (optional new flag)
Logs of updates (on /opt/e17)
Ask for confirmation, after it shows what will be done.
Only outputs information header report once (3 times on the original!)
Only do CVS updates of the chosen e17 libs/apps/modules.
Only compiles libs/apps/modules that have been updated on cvs.
You can get the original here and patch here.
Apply it with: | Code: | | patch easy_e17.sh easy_e17.patch.txt |
(NEW->) Now It just compiles libs or/and apps (and they dependencies) that have been updated on cvs.
Hope some of you find it usefull. Is not very well tested, but must be ok (...said the guy entering on the zeppelin  )
If you find problems with the new patch, i keep the old version (for 1.0.3) here.
 Don't forget that you need to remove old installations of e17 made with emerge!!
_________________
ESTRAGON: We've lost our rights?
VLADIMIR: (distinctly) We got rid of them. |
|
| Back to top |
|
|
sfragis
Tux's lil' helper
Joined: 24 Mar 2005
Posts: 95
Location: RE < IT < Europe
|
| Posted: Fri Aug 11, 2006 1:20 pm Post subject: |
|
|
Hi all, I'll give my contribute to the noble cause of E17 with the nth build script 
You can download it from here.
Some parts of the code are brutally copied from other scripts, I hope anybody won't mind it .
As many other scripts do, this one uses portage ebuilds.
What makes it helpful for me is that: all of the ebuilds that fail during compilation or checkout are written in a file; that file can be submitted later to the script which tries to emerge them only.
I use it on a monthly basis.
_________________
Regards
Fabio Strozzi |
|
| Back to top |
|
|
hanhun
n00b
Joined: 24 Dec 2004
Posts: 30
|
| Posted: Thu Oct 12, 2006 3:46 am Post subject: |
|
|
| great! |
|
| Back to top |
|
|
|
Desktop Environments
