Hello Thomas, Thanks for your prompt reply and clarifying it in details...
I understand that easy_17 is not part of enlightenment development and it is a third part script which download and install. Lets keep easy_17 topic aside for the moment and I would like to know if I am interested in latest e17 functionalities to use and report bugs as an end user then I can able to build e17 code using Makefile.linux which builds the following packages as below e e_dbus eet efreet embryo python-ecore python-edje ecore edje eeze eina evas python-e_dbus python-evas If I want to build remaining supported applications such as enjoy, elementary and so on. Do I need to go to individual folders and compile and install ? If so, is there other way to do it in one short ? Sorry for the inconvenience, I am trying to get all the packages to install and keep them up to date. Thanks in advance. > ------------------------------------------------------------------------------ > > This SF email is sponsosred by: > > Try Windows Azure free for 90 days Click Here > > http://p.sf.net/sfu/sfd2d-msazure > > _______________________________________________ > > enlightenment-users mailing list > > enlightenment-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > > Hello Suresh, > > you really got a few things mixed up here. > Easy_e17.sh is by no means a build system, and certainly not > Enlightenments build system. > Most of enlightenments sub-projects (libraries, applications, modules, > ...) use autofoo (automake, autoconf, and consorts) as a build system. > The build system is per application, not for the whole SVN. > That's not the buildsystems job and so it will never be done. > > Easy_e17 however is used to build and install all supported > applications in E's SVN by using their build systems. Therefore it is > more similar to a simple package manager than a build system. It > generally works well and is actively being developed, so if you report > bugs they likely will get fixed. As E SVN does change often and > quickly, it is necessary to change Easy_e17 now and then, too. > > Endusers should not use SVN if they expect things to "just work" and > so they should not use Easy_e17 unless they're willing to at least > report bugs. It is the distributions job to provide the packages for > those users. There is no excuse for any distribution not to include > the Enlightenment Libraries (EFL), as they experience regular > releases. E17 itself has not yet been released, but released snapshots > could be easily used for packaging by distributors. > > The Makefile.linux in E's root directory only builds a small set of > packages and thus is not comparable to Easy_e17. > > ~thomasg > > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > enlightenment-users mailing list > enlightenment-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > -- -Regards, Suresh ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
