Eric Sandall wrote: > 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>?
Nah. Doesn't work like that ATM :/ But it's possible to make 'e_modules=/dir ./configure' work. If that's a good solution, I will fix it (if I get the time...) Sebastian ------------------------------------------------------------------------- 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