[E-devel] Using the release name in paths in e17
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
Re: [E-devel] Using the release name in paths in e17
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 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. As annoying as you may find it, that's not a blocking issue. You can get the release number using `pkg-config --variable=release enlightenment` Regards, -- Albin Tonnerre signature.asc Description: Digital signature -- 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
Re: [E-devel] Using the release name in paths in e17
On Sat, Dec 5, 2009 at 4:13 PM, Albin Tonnerre albin.tonne...@gmail.comwrote: 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 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. As annoying as you may find it, that's not a blocking issue. You can get the release number using `pkg-config --variable=release enlightenment` Regards, -- Albin Tonnerre -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQIcBAEBCAAGBQJLGmpzAAoJEBEG8gBbtuSlCAQQAKv4Vfgh074DDvp9/RhxMln9 SCweuS3mKcrZjsKELGIrRxP6B0lUjW7mYvTtV4eE0QbKZzGF/vkE6JyaWzhc6guw Inz859RP7PZmJLVzVibvkEqBI0+cc+7RJn28YvlhDHo9x/whHmTWmS/nb2QvDjae /n5szZWYatiMGj4bbKAUSCwTWJyAlTsJ0F3ScNWs7WCIrfUs3Va/JRNdKa9D0E84 oKTpqkPCu/ZsLgNkiamwMwV6UV3oZ49cFyZ9ftkESjBSs3tXP6CJ262RO3QlVhVr Co6wb/PuCAl/57taG9IAXa6f0NJyM7MQuKZJyUlw9mvRHZdx0LtJjx+IxJtqWnVx FONYOIlHeDMFqC8FkxnoqIOxY/5X5RLdCqw0RfiYbqrm8/eg2q/OuKFD1LagXejZ Pf9o9XTrMB3i/yBaDo6klI0L7XGaebawvIyt5iHryzL9Y6GKlNXLBW+aBvHj1SUX IpoQTh8LK5QKfEmq5bs24XszHbjxRJ2k5d8kHoKSxHMZuVuAntVIKYKbWKVXChfV Ufg790Na08p4uKQjy7f+i7pofPMVVu1b8M+VeTQh5ZQiMkz5pNKNJyi/BITH7oA9 u8dznNnz4OjiQqm3oy2tM/ChWn8dBvBHEXPOBP4dTOY2J2QrAFB6T3nRRkhfV81C ic97yRt39Qnxdk5KoWxE =G3MS -END PGP SIGNATURE- Nice, that's a good tip :P Though still, what's the rationale behind it? -- 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
Re: [E-devel] Using the release name in paths in e17
On Sat, 5 Dec 2009 16:19:03 +0200 Tom Hacohen t...@stosb.com 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 releases of e... and we could have broken compatibility (abi) between them - thus the release name there to ensure the module is built against the release you are using -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- 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
Re: [E-devel] Using the release name in paths in e17
On Sat, Dec 5, 2009 at 5:00 PM, Carsten Haitzler ras...@rasterman.comwrote: On Sat, 5 Dec 2009 16:19:03 +0200 Tom Hacohen t...@stosb.com 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 releases of e... and we could have broken compatibility (abi) between them - thus the release name there to ensure the module is built against the release you are using -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com OS + CPU: I get it, makes sense. Version: Makes less sense, but enough to make it worth it :P Thanks, please close the ticket. -- 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
