[prev in list] [next in list] [prev in thread] [next in thread] 

List:       enlightenment-users
Subject:    Re: [e-users] usage of ~/.e/e/modules
From:       Carsten Haitzler (The Rasterman) <raster () rasterman ! com>
Date:       2005-07-30 2:25:47
Message-ID: 20050730112547.061bf5d7 () icky
[Download RAW message or body]

On Fri, 29 Jul 2005 19:26:01 +0000 Jason Melbye <jdmelbye@wisc.edu> babbled:

> On Mon, 25 Jul 2005 20:47:30 -0500
> Chad Kittel <vertigo@wi.rr.com> wrote:
> 
> > How does one make use of a user's ~/.e/e/modules directory?
> > 
> > Lets use the engage module as an example.  Currently when engage gets
> > compiled and installed the following files end up in the following
> > places in the file system.
> > $PREFIX/bin/engage
> > $PREFIX/lib/engage/module/module_icon.png
> > $PREFIX/lib/enlightenment/modules_extra/engage/linux-gnu-i686/module.a
> > $PREFIX/lib/enlightenment/modules_extra/engage/linux-gnu-i686/module.la
> > $PREFIX/lib/enlightenment/modules_extra/engage/linux-gnu-i686/module.so
> > $PREFIX/share/engage/icons/xapp.eap
> > $PREFIX/share/engage/themes/gentoo.edj
> > $PREFIX/share/engage/themes/module.edj
> > $PREFIX/share/engage/themes/none.edj
> > 
> > How would a regular user have taken engage, compiled it himself from
> > his home directory and then placed it into his ~/.e/e/modules directory?
> > 
> > Would it be as simple as making an engage/linux-gnu-i686/ directory
> > there (so now you have ~/.e/e/modules/engage/linux-gnu-i686/) and
> > placing all three module.[a|la|so] files in there?  
> > 
> > What about any .edj theme files that go with the module?  Do they (the
> > module.edj file in this example) just go into
> > the ~/.e/e/modules/engage/linux-gnu-i686/ directory as well?
> > 
> > Thank you,
> > Chad
> > 
> 
> That's an interesting question.  Is that what the ~/.e/e/modules directory was
> intended for?  Anyone know?

yes. ~/.e/e/modules was for a users own  install of modules if they don't have
root access or don't want to install on the system anywhere other than for
themselves.

the intent is all 3rd party modules should be able to install anywhere the user
asks them to be - in fact they likely should have it as a configure option.
since no one is making stand alone 3rd party modules (except for engage) and
just are lumping them all into e_modules you have no good examples to use. i
suggest that the e_modules be split into separate independent build trees.
modules should have an option for user install or system install. i always say
system installed modules going into PREFIX/lib/enlightenment/modules where e
itself installed included modules, just that you can add more later from other
sources. and all other modules (user modules) being installed in ~/.e/e/modules.
of course modules could install anywhere, BUT then you would have to add their
base dir to the module dir list so e will find them when you do a simple
enlightenment_remote -module-load blah instead of having to use a full path to
it. actually i should remove the full path support to force people to do things
more cleanly :)

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    raster@rasterman.com
裸好多                              raster@deephackmode.org
Tokyo, Japan (東京 日本)


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
[prev in list] [next in list] [prev in thread] [next in thread]