On 08/30/2012 01:22 AM, Gustavo Sverzut Barbieri wrote: > I dislike this patch as the suggested approach by systemd is to get the > header and implementation of sd-daemon into your project. See other > projects. This API is not changing and it's a thin layer to just access > some envvars to get fds and write back some messages. It should be also > always auto enabled, as the runtime detection is fast and should work in > BSD as well. > > If you consider this the patch would be 5 lines.
That's true, and that is easily fixed. > Last, is that all the integration we are doing? Come on, I'd expect at > least the startup and shutdown applications to be handled by systemd > --user. And our internal darmons (fm, thumbailer, cserve2, ...) Ultimately > e_exec of desktops could be managed by it (but I believe systemd lacks this > ATM). All I wanted to accomplish here is to have reliable startup notification of e17 "being ready". By being ready I understand "e17" being able to process events. My very limited (and possibly flawed) understanding of X11 suggests that should be "correct". (No, I don't care about modules loading in background. I don't think I should, that is.) I can drop autoconf easily, real question is at which point of e17 existence it should say "hi, I'm ready". My first attempt was to just do it idle loop, but it was ugly and broken so badly that I didn't really want to submit that. However, I didn't find time to take a look at this for second time, and the patch starts to age... You have to note that I'm low-level/embeeded integrator type of guy who just wanted to use systemd notification instead of (believe me) really ugly hacks that we have on our system. I can do some monkey coding, but I do lack any kind of e17 knowledge. Thus, any advice is really appreciated. Regards, -- Karol Lewandowski | Samsung Poland R&D Center | Linux/Platform ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
