Re: [E-devel] e_module-notification installation location
On Thu, 28 Feb 2008 10:14:19 +0100 (CET) [EMAIL PROTECTED] babbled: Then I agree. But --prefix should then be taken literally, so that using --prefix=/mydir makes the module end up in /mydir/MODULENAME. this would violate the principle of least surprise. --prefix should do what it does every else in autofoo - people should be able to use ./configure --prefix=/opt/blah/e make make install for everything in efl - for that matter, every piece of software that uses autofoo, and it should do the right thing and just work - install in the right place. -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
this would violate the principle of least surprise. Well said. U... then again, setting a size load option on an image and getting -- surprise! it may or may not be what you asked for! does seem to flaunt that excellent principle you want to adhere to. :) PS. Not to mention the various situations where it's hurting you efficiency wise - in both mem and performance. _ Find what you want and get it for less with an online auction. Click now! http://thirdpartyoffers.juno.com/TGL2121/fc/Ioyw6i3n7Vg4peFzfZABnf0WEB9YUbScPl2JV6cogqskHyo7Fiq9Lq/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
Michael Jennings wrote: On Tuesday, 26 February 2008, at 23:08:23 (-0800), Eric Sandall wrote: It works for me, ... so what is the better method you propose? The other e_modules just use --prefix=/usr, will that also work for your /usr/lib64 scenario? See below. 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 I have removed using --prefix during ./configure for all E17 modules. Thank you for the feedback. :) -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/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
Carsten Haitzler (The Rasterman) wrote: On Thu, 28 Feb 2008 10:14:19 +0100 (CET) [EMAIL PROTECTED] babbled: Then I agree. But --prefix should then be taken literally, so that using --prefix=/mydir makes the module end up in /mydir/MODULENAME. this would violate the principle of least surprise. --prefix should do what it does every else in autofoo - people should be able to use ./configure --prefix=/opt/blah/e make make install for everything in efl - for that matter, every piece of software that uses autofoo, and it should do the right thing and just work - install in the right place. But this case is solved by using E_CONFIG='/opt/blah/e/bin/e-config' ./configure What we now try to solve is when a user adds /my/module/dir to the module search path. We could use ./configure --with-module-dir=/my/module/dir Then we ignore all standard options :) Sebastian - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
On Fri, 29 Feb 2008 06:35:37 +0100 Sebastian Dransfeld [EMAIL PROTECTED] babbled: Carsten Haitzler (The Rasterman) wrote: On Thu, 28 Feb 2008 10:14:19 +0100 (CET) [EMAIL PROTECTED] babbled: Then I agree. But --prefix should then be taken literally, so that using --prefix=/mydir makes the module end up in /mydir/MODULENAME. this would violate the principle of least surprise. --prefix should do what it does every else in autofoo - people should be able to use ./configure --prefix=/opt/blah/e make make install for everything in efl - for that matter, every piece of software that uses autofoo, and it should do the right thing and just work - install in the right place. But this case is solved by using E_CONFIG='/opt/blah/e/bin/e-config' ./configure What we now try to solve is when a user adds /my/module/dir to the module search path. We could use ./configure --with-module-dir=/my/module/dir Then we ignore all standard options :) i'd definitely vote for that way - not overloading --prefix to behave differently to how it normally does :) Sebastian - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
Carsten Haitzler (The Rasterman) wrote: On Tue, 26 Feb 2008 12:18:26 -0800 (PST) Eric Sandall [EMAIL PROTECTED] babbled: as such modules should install in the default prefix e installed in. a module as such should NOT rely on its installation prefix ever at runtime, SO i could do: mkdir ~/tmp-stuff ./configure --prefix=~/tmp-stuff make make install mv ~/tmp-stuff/lib/enlightenment/modules/MODULENAME ~/.e/e/modules/ rm -rf ~/tmp-stuff and it should work. always. modules should be able to move anywhere after compilation. not being able to do so is a bug in the module. :) 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. Sebastian - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
lok wrote: snip As I already said it before, calling ./configure with no --prefix will use this path. You don't need it. Moreover the other modules doesn't take the --prefix=/usr option. They override it and goes in enlightenment's module dir anyway. If you run the configure with --prefix=/tmp they go in /usr/lib/enlightenment/module The only flag able to change that is --enable-homedir-install which is also supported in the notification module. The notification module, and probably any other module, works from anywhere. So even installed in /foo/bar, the only thing required to make them work is to add /foo/bar in the list of modules search path. All I did is enable the usual behaviour of the --prefix option in this module. But since it seems to trouble a lot of people that this flag actually do it's job. I can also remove the option and end all this. Sorry, I must have misunderstood the earlier post about --prefix, then. I will remove all --prefix uses from our module build process. Thanks! :) -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/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
On Tuesday, 26 February 2008, at 23:08:23 (-0800), Eric Sandall wrote: It works for me, ... so what is the better method you propose? The other e_modules just use --prefix=/usr, will that also work for your /usr/lib64 scenario? See below. 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 -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ [EMAIL PROTECTED] Linux Server/Cluster Admin, LBL.gov Author, Eterm (www.eterm.org) --- Perhaps the words are more important than the man. -- Kahless, ST:TNG, Rightful Heir - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
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/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
On Tuesday, 26 February 2008, at 12:18:26 (-0800), Eric Sandall wrote: 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). This is wrong and causes other problems. Consider, for example, /usr/lib64. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ [EMAIL PROTECTED] Linux Server/Cluster Admin, LBL.gov Author, Eterm (www.eterm.org) --- Whoa. Somebody computer programmers think is anti-social? That I'd like to see.-- Sydney Penny, Hyperion Bay - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
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/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
On Tuesday 26 February 2008 12:30:11 Michael Jennings wrote: On Tuesday, 26 February 2008, at 12:18:26 (-0800), Eric Sandall wrote: 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). This is wrong and causes other problems. Consider, for example, /usr/lib64. Michael My x86_64 box also installs to /usr/lib. Example, e_module-echo installs to / usr/lib/enlightenment/modules/echo/linux-gnu-x86_64. -sandalle signature.asc Description: This is a digitally signed message part. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
On Tue, 26 Feb 2008 12:18:26 -0800 (PST) Eric Sandall [EMAIL PROTECTED] babbled: as such modules should install in the default prefix e installed in. a module as such should NOT rely on its installation prefix ever at runtime, SO i could do: mkdir ~/tmp-stuff ./configure --prefix=~/tmp-stuff make make install mv ~/tmp-stuff/lib/enlightenment/modules/MODULENAME ~/.e/e/modules/ rm -rf ~/tmp-stuff and it should work. always. modules should be able to move anywhere after compilation. not being able to do so is a bug in the module. :) 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/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
On Tuesday, 26 February 2008, at 17:50:39 (-0800), Eric Sandall wrote: My x86_64 box also installs to /usr/lib. Example, e_module-echo installs to / usr/lib/enlightenment/modules/echo/linux-gnu-x86_64. So? Just because you do it one way doesn't mean everyone does it the same way. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ [EMAIL PROTECTED] Linux Server/Cluster Admin, LBL.gov Author, Eterm (www.eterm.org) --- Map out your future, but do it in pencil. -- Jon Bon Jovi - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
Michael Jennings wrote: On Tuesday, 26 February 2008, at 17:50:39 (-0800), Eric Sandall wrote: My x86_64 box also installs to /usr/lib. Example, e_module-echo installs to / usr/lib/enlightenment/modules/echo/linux-gnu-x86_64. So? Just because you do it one way doesn't mean everyone does it the same way. Michael It works for me, so what is the better method you propose? The other e_modules just use --prefix=/usr, will that also work for your /usr/lib64 scenario? -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/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
On Monday 28 January 2008 17:29:01 Sebastian Dransfeld wrote: Eric Sandall wrote: snip 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...) As long as it is standard across all the modules and documented, any way you guys like is fine by me. :) -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 signature.asc Description: This is a digitally signed message part. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
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/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
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/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
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. 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? Sebastian - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
This seems to be a bug with the autofoo stuff, some recent commit to all modules autofoo break the --prefix rule, it isn't respected anymore and so modules are installed in a default path. Someone should fix that... Greets, Brian 'morlenxus' Miculcy On Thu, Jan 24, 2008 at 12:50:21PM -0800, Eric Sandall wrote: Hey all, After updating lately (2008-01-24 at 10:30 PST, though the last update was a week ago or so), I noticed that notification no longer loads (E17 complains it cannot find the module). I looked at the installation path and it is now installing to /usr/notification/ instead of /usr/lib/enlightenment/modules/notification/ where all of the other modules install given the same ./configure --prefix=/usr. I recall a recent (last few days) CVS update to notification to change installation paths, but I've already deleted it. :( Thanks, -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/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
For most modules prefix is ignored, they will by default install in the enlightenment dir ($e_prefix/lib/enlightenment/modules) unless homedir is specified. With notification prefix was enabled again with the commit a while ago, but you can't give /usr as prefix, you must give the whole path which is /usr/lib/enlightenment/modules/ in your case. Giving prefix has little meaning with modules as e only looks in specific dirs for modules anyway. Sebastian Brian 'morlenxus' Miculcy wrote: This seems to be a bug with the autofoo stuff, some recent commit to all modules autofoo break the --prefix rule, it isn't respected anymore and so modules are installed in a default path. Someone should fix that... Greets, Brian 'morlenxus' Miculcy On Thu, Jan 24, 2008 at 12:50:21PM -0800, Eric Sandall wrote: Hey all, After updating lately (2008-01-24 at 10:30 PST, though the last update was a week ago or so), I noticed that notification no longer loads (E17 complains it cannot find the module). I looked at the installation path and it is now installing to /usr/notification/ instead of /usr/lib/enlightenment/modules/notification/ where all of the other modules install given the same ./configure --prefix=/usr. I recall a recent (last few days) CVS update to notification to change installation paths, but I've already deleted it. :( Thanks, -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/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
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 added it, with a little resume when the configure ends, so that people notice where the module will be installed. If you run the configure with no prefix option the behaviour is still the same, and the module will be installed in your E's dir. I didn't updated all the modules because I don't know what the other devs are thinking about this. And I don't want to impose such a thing to them without even asking. Personnaly I don't care to keep or not this option (it's maybe better if every modules act in the same manner ?). So what do you think about this ? Brian 'morlenxus' Miculcy wrote: This seems to be a bug with the autofoo stuff, some recent commit to all modules autofoo break the --prefix rule, it isn't respected anymore and so modules are installed in a default path. Someone should fix that... Greets, Brian 'morlenxus' Miculcy On Thu, Jan 24, 2008 at 12:50:21PM -0800, Eric Sandall wrote: Hey all, After updating lately (2008-01-24 at 10:30 PST, though the last update was a week ago or so), I noticed that notification no longer loads (E17 complains it cannot find the module). I looked at the installation path and it is now installing to /usr/notification/ instead of /usr/lib/enlightenment/modules/notification/ where all of the other modules install given the same ./configure --prefix=/usr. I recall a recent (last few days) CVS update to notification to change installation paths, but I've already deleted it. :( Thanks, -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/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
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 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e_module-notification installation location
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. dh - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
