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 write my own app with pages for the wizard module, I can't. I'll have to manually set the module arch if I want it to install to the proper place (because of the release version). I don't get what is it for anyway, I can hardly get the module_arch in general, but at least, if you use that, what's the release for? making sure people don't stuff modules after backwards compatibility is broken? In conclusion I see this as a bug in design that's blocking us from effectively installing 3rd party modules. Example for a path now: (on my arm device) /usr/lib/enlightenment/modules/wizard/linux-gnueabi-arm-ve r-pre-svn-05/ What it should have been: /usr/lib/enlightenment/modules/wizard/ or at least /usr/lib/enlightenment/modules/wizard/linux-gnueabi-arm/ Thanks a lot." Is there any specific reason for this behavior? I want to understand the rationale if there is one. Thanks, -- Tom. ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel