D. Hageman wrote: > > I guess the real questions that should be asked: > > a) How many non-standard libaries does one project need to support > their project? At what point are there too many? >
Define non-standard. None of the efl libraries are 'standards'. We separate things into libraries because it makes sense. Dumping everything into one bucket just makes it harder to figure out how to use something. You're just bloating a library that is suppost to be a small core library with a lot of extra crap. When does it stop? Should we put an rss parsing engine into ecore because we want to use it on the e17 desktop? > b) At what point do all the dependencies start being such a headache > that a normal user wouldn't waste their time with the software no matter > how "cool" it is? At what point does a 'normal' user install from CVS? They just do apt-get install enlightenment and walk away. Dependencies shouldn't be an issue for 'normal' users. If you're installing from CVS you're, by definition, not a normal user. > > c) How many applications are created and used by people that rely on E > libraries, but don't use E? You could ask that question about any set of libraries. The core developers are obviously E users. E also isn't released. Therefore most of the apps are going to be run by people using E. That doesn't mean we should _force_ people to use E to use any EFL apps. That's just plain stupid. > > I think C is the big question to ask. I have yet to find anyone using > an application that uses e17 libaries that doesn't use E already. What > does that indicate? Take a step back and think about it ... I am not > trying to start a fight, but rather give some perspective on things from > an end user point of view. > > If I were you ... I would just put it in ecore and be done with it. > There are people using the EFL that don't use E. I know of at least one of the devs that doesn't run enlightenment. Just because people don't do it currently doesn't make any sense. Stuffing the kitchen sink into ecore isn't the way to go. The code still has to be stabilized. It still has to be installed. The only difference is your package manager adds another dependency line. We're not adding external dependencies. This is an EFL lib that doesn't link to anything else. dan ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
