On Sat, Dec 5, 2009 at 5:00 PM, Carsten Haitzler wrote:
> On Sat, 5 Dec 2009 16:19:03 +0200 Tom Hacohen said:
>
> > Though still, what's the rationale behind it?
>
> 1. module arch and os is needed as moduels can be installed in ~/ - and ~/
> can
> be mounted on multiple architectures (eg via nfs
On Sat, 5 Dec 2009 16:19:03 +0200 Tom Hacohen said:
> Though still, what's the rationale behind it?
1. module arch and os is needed as moduels can be installed in ~/ - and ~/ can
be mounted on multiple architectures (eg via nfs). and thus... multiple
systems.. and they could have multiple releas
On Sat, Dec 5, 2009 at 4:13 PM, Albin Tonnerre wrote:
> On Sat, 05 Dec 2009 15:58 +0200, Tom Hacohen wrote :
> > "Hey, ATM there's that weird module arch in the path of the modules:
> > MODULE_ARCH="$(host_os)-$(host_cpu)-$(release)"
> >
> > For instance, if I want to be able to write my own app
On Sat, 05 Dec 2009 15:58 +0200, Tom Hacohen wrote :
> "Hey, ATM there's that weird module arch in the path of the modules:
> MODULE_ARCH="$(host_os)-$(host_cpu)-$(release)"
>
> For instance, if I want to be able to write my own app with pages for the
> wizard module, I can't. I'll have to manual
Hey,
What do you guys think about this bug I opened:
http://trac.enlightenment.org/e/ticket/474 ?
It's really serious in my pov.
Summary:
"Hey, ATM there's that weird module arch in the path of the modules:
MODULE_ARCH="$(host_os)-$(host_cpu)-$(release)"
For instance, if I want to be able to