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
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
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
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
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
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
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
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
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
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
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
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
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
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 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
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
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
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
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
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
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
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
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
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
24 matches
Mail list logo
