Quoting [EMAIL PROTECTED]: <snip> > Nah. > > It didn't work very well, as we want all module data in the module dir. > Which includes locale files etc. With the old approach locale info went in > standard dirs, and the module ended in the right dir because it assumed > what e's module dir was. So if the module dir changed, we had to update > all modules. > > But, can't people just do 'e_module=/dir make install' and the module will > install wherever you want?
If that's the proper method then I will change our packages to use that. ;) Will all e_module packages support e_module=<dir>? -sandalle -- Eric Sandall | Source Mage GNU/Linux Developer [EMAIL PROTECTED] PGP: 0xA8EFDD61 | http://www.sourcemage.org/ http://eric.sandall.us/ | http://counter.li.org/ #196285 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
