On Mon, 2 Dec 2013 11:57:23 +0900 Cedric BAIL <[email protected]> wrote:
> So I have Ecore_Avahi ready in a branch for inclusion in 1.9. I am > just wondering if I should make it a strong dependency or an optional > one. I am thinking about making it a needed dependency, any though > against that ? For those that don't know Avahi is a network service > announcement/browsing library around zeroconf and Ecore_Avahi is just > there to do the mainloop integration. It means we can avoid using > Avahi glib integration to do the same. I don't use Avahi. I've removed most of it from my desktop system. The bits that are left I can't remove coz it's integrated into half of everything. Why most of that stuff needs any sort of network integration is a mystery to me, it doesn't. It just depends on Avahi coz people thought "hey, every one needs Avahi". I'll bet that most people don't even know what it is (or any other zeroconf type system), and never actually use it. Now if there was some sort of zeroconf integration that didn't need mainloop support, and could easily support "library doesn't exist, so skip that", then that would be much better. Then I can remove all of it from my system. B-) > In the mean time I have started working on integrating libassh within > Ecore, in a Ecore_Con_SSH library. I don't think that I will make it > for 1.9, but not sure yet. The question for this one is a little bit > different, libassh is pretty young and not included in any > distribution as far as I know. So should I do like we do with some > library and put it in our tree and keep it in sync, or should I make > it an optional library (at this stage it is not going to be a strong > dependency) ? What does it even do? > Opinion ! Keep it all optional please. Every little extra non optional library added just bloats things out more for people that don't use that stuff. Sooner or later we'll be just as bloaty as GNOME or KDE. My embedded work particularly can do without every little extra library being added. Especially the stuff with a legally mandated "only include the stuff that is actually needed" requirement. Or to put it another way, if the government asks my client "Why does your machine include stuff for automated network discover and ssh, is that some sort of backdoor?", and all my client can say is "No idea, it's not actually used.", then the government says "Not approved.", and my client goes out of business. Government LAWS can be tough like that. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world.
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
