Michael Jennings wrote: > On Wednesday, 27 February 2008, at 09:20:59 (+0100), > Sebastian Dransfeld wrote: > > >> Or just ./configure --enable-homedir-install >> >> I did some work so that the modules should end up in either the >> current homedir, or the path enlightenment-config points to. And >> that everything the module installs ends up in the same moduledir. >> > > Exactly. --prefix doesn't really make sense for modules. They either > go into E's module directory or the user's module directory. Nothing > else makes sense. > > Michael > > What doesn't makes sense here ? Someone can set up the search path for the modules to use only /foo and remove the defaults dirs. Block the installation to the default path would be like forcing the installation of any application to either be in / or /usr and nowhere else.
I agree that set up e's dir as a default path to install a module is useful but the --prefix is only an option, blocking it just reduce the posssibilities when installing. ------------------------------------------------------------------------- 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
