Hi,

I would like to announce here the availability of Slackware packages
for the Enlightenment 0.17 window manager, aka SlackE17 project.

The code of E17 is still in heavy development but the WM does really
look good and, except for the file manager, it is stable enough for
every day use.

You can download the packages, and the slackbuild scripts, on the
SourceForge project page:

http://sourceforge.net/projects/slacke17

There is a release every month, this is the third one.

This should be apply on Slackware 10.2

Feel free to send any comment

Regards,

--
Jerome Pinot (ngc891)

On 2005-12-01, ngc891@gmail.com <ngc891@gmail.com> wrote:
> Hi,
>
> I would like to announce here the availability of Slackware packages
> for the Enlightenment 0.17 window manager, aka SlackE17 project.
>
Thanks for the effort! I have E17 installed and ran it for a few months.
(enlightenment-0.17.0_cvs20050823) Would be nice to see whats new.

> The code of E17 is still in heavy development but the WM does really
> look good and, except for the file manager, it is stable enough for
> every day use.
>
Agreed, even the snapshot that I have above was very stable. I can't wait for
it to be done. I sure hope they implement tabs (ala fluxbox) I talked to one
of the devs in #e on freenode, and he said it was one the todo, but not high
priority. As for the filemanager evidence. I ran this a long time before I
installed E17. It stands well on it's own, and has some really neat features.

> You can download the packages, and the slackbuild scripts, on the
> SourceForge project page:
>
> http://sourceforge.net/projects/slacke17
>
Thanks for letting us know. I had mentioned E17 a few months ago, and a few
asked about where to get packages. Now we have a place.

> There is a release every month, this is the third one.
>
> This should be apply on Slackware 10.2
>
> Feel free to send any comment
>
How are you building the packages? Are you using
slackpkg|checkinstall|buildscripts? IMHO it would be great if you could provide
some SlackBuild scripts for the people that like to go that root.

What kind of machine are you building the packages on. Not processor/mobo, I
mean, is it a "clean" slack install, with no 3rd party libs that may have been
used. Are all of the dependencies met via the provided packages?

I'll check out your packages as soon as I can.

--
Best Regards,

Mike Reynolds

MikeReynolds wrote:
> On 2005-12-01, ngc891@gmail.com <ngc891@gmail.com> wrote:

>>You can download the packages, and the slackbuild scripts, on the
>>SourceForge project page:

......

> How are you building the packages? Are you using
> slackpkg|checkinstall|buildscripts? IMHO it would be great if you could provide
> some SlackBuild scripts for the people that like to go that root.
^^^^^^^^^^
The answer was there already.

> What kind of machine are you building the packages on. Not processor/mobo, I
> mean, is it a "clean" slack install, with no 3rd party libs that may have been
> used. Are all of the dependencies met via the provided packages?

A very valid question. Many packagers introduce hidden dependencies
into their packages by building on unclean Slackware installs.

I will check it out for sure, wanted to build e17 myself for a long
time now, and quit at an early stage.

Eric

On 2005-12-01, Eric Hameleers <alien@sox.homeip.net> wrote:
> MikeReynolds wrote:
>> On 2005-12-01, ngc891@gmail.com <ngc891@gmail.com> wrote:
>
>>>You can download the packages, and the slackbuild scripts, on the
>>>SourceForge project page:
>
> .....
>
>> How are you building the packages? Are you using
>> slackpkg|checkinstall|buildscripts? IMHO it would be great if you could provide
>> some SlackBuild scripts for the people that like to go that root.
> ^^^^^^^^^^
> The answer was there already.
>

Doh, thanks for pointing that out.
/me cleans his glasses

>> What kind of machine are you building the packages on. Not processor/mobo, I
>> mean, is it a "clean" slack install, with no 3rd party libs that may have been
>> used. Are all of the dependencies met via the provided packages?
>
> A very valid question. Many packagers introduce hidden dependencies
> into their packages by building on unclean Slackware installs.
>
> I will check it out for sure, wanted to build e17 myself for a long
> time now, and quit at an early stage.
>

Which is part of the problem at linuxpackages.net IMHO. Not so much that there
are other deps, just that they may not be listed.

--
Best Regards,

Mike Reynolds

>> What kind of machine are you building the packages on. Not processor/mobo, I
>> mean, is it a "clean" slack install, with no 3rd party libs that may have been
>> used. Are all of the dependencies met via the provided packages?
>
>A very valid question. Many packagers introduce hidden dependencies
>into their packages by building on unclean Slackware installs.

Yeah, all the dependencies are in the vanilla Slackware 10.2 (and last
patches) and the packages. That's why I had to add SQLite for Eclair in
the last release.

I package with SlackBuild all the software I'm using on the box, and
before building anything I want to distribute, I start by removing
_all_of_them_.

So the process of building SlackE17 is quiet long

Binaries are build with GCC 3.4.4 and -march=i486 -mtune=i686 CFLAGS
(check the READMEs)

--
Jerome Pinot
http://ngc891.blogdns.net