On Fri, 25 Jan 2008, Christopher Michael wrote: > Sebastian Dransfeld wrote: >> lok wrote: >>> It's not a bug the configure.in are set up this way in most (all?) modules. >>> They will be installed in `enlightenment-config --module-dir`. >>> Unless you use the --enable-homedir-install option. >>> Morlenxus pointed me than the --prefix was ignored, and I thought that it >>> might be a handful option for package maintainers (or people with >>> various reasons). >> >> I think package maintainers would like modules to install in a location >> where e finds it, so I don't really think we should use --prefix. At >> least since modules don't use --prefix like normal apps do. For most >> users it isn't logical that ./configure --prefix=/usr in 'e_modules' >> wont work with ./configure --prefix=/usr in 'e'. >> >> Maybe a --set-module-installation-dir option? >> >> >> Sebastian > > Well, before the great autofoo changes, this used to work. If you passed > in a prefix (eg: same prefix as E) it would install to the module > directory under E. If you did not pass a prefix, then it installed to > the user's home directory (under ~/.e/e/modules) which is a place that E > also checks.
For now I've modified the e_module-notification package to specify --prefix=/usr/lib/enlightenment/modules. I will remove that once this is fixed (or add it to all other modules if they are changed). -sandalle -- Eric Sandall | Source Mage GNU/Linux Developer [EMAIL PROTECTED] | http://www.sourcemage.org/ http://eric.sandall.us/ | Build/Release Engineer @ Cisco/WebEx http://counter.li.org/ #196285 | http://www.webex.com/ ------------------------------------------------------------------------- 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
