I'm haveing a strange issue with the pager popup when shifting desktops (see
attached) - the image seems corrupted somehow. This is only occuring with
the japan2007 theme, I've tried disabling bling, dropshaddow, rebuilding the
theme, etc. - and the popup still looks like this. Anyone have any
Starting xmms on current CVS build causes e17 to completely freeze.
Onefang thinks it may be due to the new evas threading code (this is a multi
proc / dual core box).
BT follows:
[Switching to Thread -1216890192 (LWP 17018)]
0xbfffe410 in __kernel_vsyscall ()
#0 0xbfffe410 in __kernel_vsyscall
On 9/18/06, Blake Barnett [EMAIL PROTECTED] wrote:
Personally, I don't think it's worth it. Integrating it well with
e17 is non-trivial because of deficiencies in the spec. Trayer works
fine as an alternative: http://prdownload.berlios.de/fvwm-crystal/
trayer-1.0.tar.gz
-Blake
Wouldn't
I'm getting the following warnings when building from the evas spec, it
looks like it has to do with some bad options in the Conditional build
stuff:
configure: WARNING: you should use --build, --host, --target
configure: WARNING: you should use --build, --host, --target
configure: WARNING:
Raster -
You recently changed the evas and ecore specs to disable directfb
support explicitly, is this intentional? if so is there a reason why?
On 4/12/06, Eric Sandall [EMAIL PROTECTED] wrote:
When trying to build e_utils lately (checkouts off and on over the lastfew weeks) I have been receiving this error:/usr/bin/makeall-recursiveIn file included from e17setroot.c:8:/usr/include/Imlib2.h:108: error: syntax error before '*' token
This is a known issue, inherited from the original author. The intent
was to get evolume in before the cvs move this week. The configuration
problem will be fixed once the new CVS is up.
In the mean time, if you want to remove a mixer channel from evolume,
left click it's name in the module (the
On 3/22/06, Brian Mattern [EMAIL PROTECTED] wrote:
On Wednesday 22 March 2006 14:46, phriedrich wrote:How about releasing tarballs at stable points in module dev, and stickingthose up on get-e? The modules are in cvs to facilitate development (and notas an alternative distribution method), so its
schweet, that does it :)
nice work devilhorns :)On 3/12/06, enlightenment-cvs@lists.sourceforge.net
enlightenment-cvs@lists.sourceforge.net wrote:Enlightenment CVS committal
Author: devilhornsProject : e_modulesModule: wlanDir : e_modules/wlanModified Files:e_mod_main.cLog Message:Fix values on
Are there any objections to adding evolume to e_modules in cvs?
I know originally there were concerns that evolume had dependencies
outside the scope of e17 (alsa etc.), but now that e_modules has moved
out of the e17 tree, are there any other objections?
This is an extremely useful module and I
Also keep in mind that there are other build systems your global changes affect (i.e. RPM), and while a change you make may work fine for you, it doesn't for others. If you want to make distribution packages directly from cvs checkouts, I'd reccomend doing as I did and writing a nice wrapper shell
Shadoi - FYI In the interim while you guys decide how to work this for
.debs, I've removed changelog.in from EXTRA_DIST in all of e17/libs and
e17/apps so that make dist will at least work.
Ryan
On 3/6/06, Blake B. [EMAIL PROTECTED] wrote:
My email is in most of the packages for a reason.:)You
Here are some patched files, against evolume-0.0.20, to build
evolume as an rpm, the SPEC is based on MEJ's excellent module
template spec :)
don't suppose we could convince you to submit evolume to cvs?
e_modules-evolume.spec.in
Description: Binary data
configure.ac
Description: Binary data
On 11/3/05, Ciro Mattia Gonano [EMAIL PROTECTED] wrote:
3) there should be a CVS tree like:modules/snow/battery/monitor/evolume/...
I wholeheartedly agree with this, lets either move
them to e17/modules or into the misc branch. Having the source on
get-e.org does NOT facilitate people being able
Please, if you're going to add / remove files from CVS, make sure you
take them out / add them in to EXTRA_DIST in the Makefile.am in that
dir as well :)On 10/30/05, enlightenment-cvs@lists.sourceforge.net
enlightenment-cvs@lists.sourceforge.net wrote:Enlightenment CVS committal
Author:
Someone let loose the asparagus and didn't bump versions in the specs.
Also a fix for make dist in epeg.
Patch attached, please commit :)
Ryan
Index: apps/e/enlightenment.spec
===
RCS file:
This patch (below) to the top level Makefile.am breaks making usable
dist tarballs, there's no autofoo crap in the doc subdirs so no doc
files are being copied.
I'm working on fixing that but may be a few days as I'm on the road
right now, please either reverse this patch or at least don't apply
Some spec and Makefile.am fixes for edje and e.
what's the odds of getting commit access to assist keeping this stuff up
to date?
Ryan
Index: apps/e/enlightenment.spec
===
RCS file:
On Tue, 2005-08-30 at 00:58 -0400, Michael Jennings wrote:
On Monday, 29 August 2005, at 21:53:57 (-0400),
Ryan Little wrote:
Here's a new diff against the last commit.
Please review / commit.
After much discussion with everyone, I've changed e_utils and e_modules
specs so
Here's a new diff against the last commit.
Please review / commit.
After much discussion with everyone, I've changed e_utils and e_modules
specs so everything is in one package instead of separate packages for
each module / utility. This will make it easier for people to add new
modules / utils
On Wed, 2005-08-24 at 02:44 -0400, Michael Jennings wrote:
On Wednesday, 24 August 2005, at 13:31:19 (+0800),
Didier Casse wrote:
2. With this line :%{__make} %{?_smp_mflags} %{?mflags}
Truncate the last part. It's not needed. I've learned that from
Redhat Engineers!
It should
This patch updates all libs / apps spec files to the correct versions
fixes a few Makefile.am errors that didn't build correct make dist
packages.
I've also created some very generic specs for e_modules e_utils and
elicit.
Raster: The hunk for apps/e/data/themes/images/Makefile.am may conflict
22 matches
Mail list logo
