Enlightenment

rockslinux · 10-20-2010, 06:42 PM

http://www.enlightenment.org

SlackBuilds for BETA Release of core EFL, Enlightenment, Elementary.

tar xvf enlightenment.txt

MrChilly0 · 10-20-2010, 08:48 PM

e17 is a great wm for netbooks...bring on the updates

tommcd · 10-20-2010, 08:52 PM

There is a slackbuild for enlightenment at slackbuilds.org:
http://slackbuilds.org/repository/13...enlightenment/
If you want a newer version of enlightenment you can probably just change the version number in the slackbuild script. This usually works.

D1ver · 10-21-2010, 03:56 AM

I'm going to have to look into this Enlightenment. I keep seeing screen shots and it looks amazing, but I don't really know anything about it..

AlvaroG · 10-21-2010, 08:06 AM

Does it have a system tray? last time I tried it (last year) it did not have that.

rockslinux · 10-21-2010, 10:05 AM

Quote:

Originally Posted by AlvaroG

Does it have a system tray? last time I tried it (last year) it did not have that.

Yes!
http://trac.enlightenment.org/e/wiki/FAQ
>Does E17 have a systray?
>Yes! Load Systray module, place it on a shelf and enjoy

LMB-Click on an empty desktop "Settings >> Modules >> Systray (Load)"
RMB-Click on shelf >> Contents >> Systray

AlvaroG · 10-22-2010, 08:08 AM

Great, thanks! I was not trying to bash E, I liked it when I tried it, but the lack of a systray was not good for me.
The reasoning for that at the time was that one should be using multiple desktops to keep more apps open, but the truth is that many modern apps expect to minimize to tray and actually use less resources when minimized (jdownloader is an example).

Will try E17 again

zlin50 · 10-24-2010, 10:18 AM

Hint:

if you install E17 on a Slack64 using the default path (/usr), E17 complains about not finding /usr/lib/ (yeah, true -

)

My work-around was to install under /opt/e17 - which creates libs in /opt/e17/lib/

Seems to work for me.

tpreitzel · 10-24-2010, 10:01 PM

Great to see the best desktop in existence finally go BETA! I've been using it so many years that I don't really pay attention anymore to it's status. I just use it. Although Enlightenment's been around a long time, it hasn't even begun to increase in popularity yet. It will.

rockslinux · 10-24-2010, 10:12 PM

Quote:

Originally Posted by zlin50

Hint:

if you install E17 on a Slack64 using the default path (/usr), E17 complains about not finding /usr/lib/ (yeah, true -

)

My work-around was to install under /opt/e17 - which creates libs in /opt/e17/lib/

Seems to work for me.

Thanks.
But I don't understand why so. I don't use Slackware 64-bit. How I think, need libraries (requirements) should be in /usr/lib64.
In SlackBuilds, for example enlightenment.SlackBuild, I don't make automatically determine the architecture, I'm don't need it, I set manually ARCH="i486". For other architecture need set ARCH, or replace on automatically determine. For example, on SlackBuilds.org, it's make so:

Code:

# Automatically determine the architecture we're building on:
if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) ARCH=i486 ;;
    arm*) ARCH=arm ;;
    # Unless $ARCH is already set, use uname -m for all other archs:
       *) ARCH=$( uname -m ) ;;
  esac
fi

My enlightenment.SlackBuild

Code:

ARCH="i486"   #On Slackware 64-bit need comment this
#ARCH="i686"
#ARCH="x86_64"#Uncomment it

if [ "$ARCH" = "i486" ]; then
  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
elif [ "$ARCH" = "i686" ]; then
  SLKCFLAGS="-O2 -march=i686 -mtune=i686"
elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
  LIBDIRSUFFIX="64" #This variable will use on configure for the set libdir to /usr/lib64
fi

CWD=$(pwd)
TMP=${TMP:-/tmp/SBo}
PKG=$TMP/package-${PKGNAM}
OUTPUT=${OUTPUT:-/tmp}

rm -rf $PKG
mkdir -p $TMP $PKG

cd $TMP
rm -rf ${PKGNAM}-${VERSION}
tar xvf $CWD/${PKGNAM}-$VERSION.tar.gz || exit 1
cd ${PKGNAM}-$VERSION || exit 1

# Make sure ownerships and permissions are sane:
chown -R root:root .
find . \
  \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
  -exec chmod 755 {} \; -o \
  \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
  -exec chmod 644 {} \;

# Configure:
CFLAGS="$SLKCFLAGS" \
./configure \
  --prefix=/usr \
  --libdir=/usr/lib${LIBDIRSUFFIX} \
  --sysconfdir=/etc \
  --localstatedir=/var \
  --mandir=/usr/man \
  --docdir=/usr/doc/${PKGNAM}-$VERSION \
  --build=$ARCH-slackware-linux

zlin50 · 10-25-2010, 04:37 PM

@rockslinux:

your approach most probably won't compile under slack64, since using ARCH=i486 (and /usr/lib) in a 64bit-environment will fetch the wrong libraries while linking.

Defining ARCH via "uname -m" as in the SBo-buildscript is the proper way, but results in using /usr/lib64.

rockslinux · 10-25-2010, 10:24 PM

Quote:

Originally Posted by zlin50

@rockslinux:

your approach most probably won't compile under slack64, since using ARCH=i486 (and /usr/lib) in a 64bit-environment will fetch the wrong libraries while linking.

Defining ARCH via "uname -m" as in the SBo-buildscript is the proper way, but results in using /usr/lib64.

I apologize for my terrible English. I don't understand why you say it's again.
In a previous message, I tried explain, that on Slackware 64-bit, SlackBuilds should work, but on condition, that they will slight change.

Try explain you again.
I writer it's SlackBuilds for myself. I ask on irc SlackBuilds.org, can I placed this SlackBuilds on SBo, answer "no, for Enlightenment have maintained, if you want contact with him". And I did not them into conformity with the requirements of SBo. But because I use other SlackBuilds from SBo, for me there useful use his variable, for example, TMP=${TMP:-/tmp/SBo}.
I don't use Slackware 64-bit, and I can't test my SlackBuilds on this platform, therefore I don't will add this platform by default. But, because I post this thread, I add strings
ARCH="i486"
#ARCH="i686"
#ARCH="x86_64"
and, if somebody want build EFL use my SlackBuilds, his can comment ARCH="i486" and uncomment #ARCH="x86_64".

Quote:

Originally Posted by zlin50

@rockslinux:
Defining ARCH via "uname -m" as in the SBo-buildscript is the proper way, but results in using /usr/lib64.

Me don't interest proper way, I DON'T USE SLACKWARE 64-BIT. I DON'T MAINTAINED THIS SLACKBUILDS ON SBo. IF SOMEBODY THIS SLACKBUILDS WILL USEFUL I'M GLAD, IF SOMEBODY NEED HELP WITH EFL ON X86 PLATFORM, I TRIED HELP.
Beside. I think, what use strangers SlackBuilds, not from office SBo, not from know people, don't look inside they content - very bad idea; maybe I'm crazy, and writer in SlackBuild command "rm -vr /*".

tar xvf enlightenment.txt;
cd enlightenment;
for directory in e*; do cd $directory; sed -i -e 's|ARCH="i486"|#ARCH="i486"|' -e 's|#ARCH="x86_64"|ARCH="x86_64"|' *.SlackBuild; cd ..; done

tpreitzel · 10-28-2010, 12:57 AM

Wow!

The developers have been busy improving e17 lately as well as consolidating the sources. All of the modules are now located under the enlightenment directory instead of separately. Some of my favorite modules are currently missing, though. I'll have to check the changes more thoroughly. * I've heard that Enlightenment has had assistance from a commercial enterprise for the past couple of years and it's beginning to show in greater organization and stability of e17. Nice!

* Evidently, the developers are only including "essential" modules under the enlightenment directory while still retaining the other modules separately under SVN trunk as E-MODULES-EXTRA. Regardless, the modules contained in E-MODULES-EXTRA aren't compiling at the moment. I use the easy_e17.sh script to update my sources which has changed drastically since my last use earlier this year.