Hello, I was expecting your reply :-)
On Mon, Dec 2, 2013 at 1:25 PM, David Seikel <[email protected]> wrote: > 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-) So basically a turned on by default option will do :-) And realistically you can't implement a network library without integrating it into the mainloop, that's impossible. But if you don't use it, then you don't link to it and don't initialize it, so you can skip it. >> 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? Right now up to channel setup. It does come with two setup, either using gcrypt or it's internal cipher. The internal one are limited to a small subset, but provide a functional ssh for embedded target that don't want to include and use gcrypt. Goal is to provide full feature ssh/scp support and integration with a UI toolkit. Something no other library can provide. I have spend enough time with libssh, libssh2 and friends to say they are just useless for anything UI related. >> 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. Definition of bloat may vary, for me the main issue with other DE, is that they consume so much memory and resource in general that they get in the way of what I am doing. So keeping our small footprint with more feature is not something I see as impossible as you seems to think it is. > 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. Hehe, especially when that said implementation enable to write a ssh server and a ssh client :-) That one will stay optional and disabled by default until we get to enough working feature. I didn't even upload it to a branch yet, so no hurry, but still you didn't answer the question ! -- Cedric BAIL ------------------------------------------------------------------------------ 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
