From: Fernando Meira <fmeira@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] enlightenment 16 or 17
Date: Thu, 4 Aug 2005 08:08:32 +0000 [thread overview]
Message-ID: <a3c2e88b05080401085349d2f1@mail.gmail.com> (raw)
In-Reply-To: <432beae05080315372f246f28@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2136 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 4401 bytes --]
next prev parent reply other threads:[~2005-08-04 8:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 12:45 [gentoo-user] enlightenment 16 or 17 Fernando Meira
2005-08-03 13:11 ` Luke Albers
2005-08-03 13:20 ` fire-eyes
2005-08-03 15:23 ` Luke Albers
2005-08-03 15:59 ` Christoph Gysin
2005-08-03 16:10 ` Luke Albers
2005-08-03 16:56 ` Fernando Meira
2005-08-03 17:31 ` Luke Albers
2005-08-03 16:51 ` Fernando Meira
2005-08-03 16:51 ` Fernando Meira
2005-08-03 17:33 ` Luke Albers
2005-08-04 8:57 ` Christoph Gysin
2005-08-03 17:28 ` Fernando Meira
2005-08-03 17:28 ` Fernando Meira
2005-08-03 18:33 ` Luke Albers
2005-08-03 18:55 ` Fernando Meira
2005-08-03 19:04 ` Luke Albers
2005-08-03 19:57 ` Fernando Meira
2005-08-03 22:37 ` Justin Patrin
2005-08-04 8:08 ` Fernando Meira [this message]
2005-08-04 9:16 ` Christoph Gysin
2005-08-04 17:53 ` Fernando Meira
2005-08-04 18:03 ` Luke Albers
2005-08-04 18:26 ` Fernando Meira
2005-08-04 18:36 ` Luke Albers
2005-08-04 20:10 ` Fernando Meira
2005-08-05 17:42 ` Fernando Meira
2005-08-05 18:03 ` Luke Albers
2005-08-07 23:23 ` Christoph Gysin
2005-08-04 9:00 ` Christoph Gysin
2005-08-03 13:58 ` Christoph Gysin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3c2e88b05080401085349d2f1@mail.gmail.com \
--to=fmeira@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox