They recommend you just copy their files (2) to your project. No need to detect 
and link to a library. Actually in the past you just had this option.

--Gustavo

Sent from my iPhone

On 09/09/2012, at 23:56, Carsten Haitzler (The Rasterman) 
<ras...@rasterman.com> wrote:

> On Tue, 4 Sep 2012 20:29:34 -0300 Gustavo Sverzut Barbieri
> <barbi...@profusion.mobi> said:
> 
>>> On Monday, September 3, 2012, Carsten Haitzler wrote:
>>> so you mean put this stuff in ecore?
>> 
>> could be, the trick part is trying to do this smartly in ecore, I
>> don't think it's possible.
> 
> well here i'm just thinking of the systemd "ready" notification - not socket
> activation. :) yes socket activation will need to build something like
> ecore_con or ecore_ipc server handles from existing fd's. you'll also need a
> way to know what that fd is.
> 
>> what you could use is: Ecore_XXX *ecore_XXX_from_fd(int fd), instead
>> of the existing primitives that creates the socket for server and
>> client. This one assumes they were created, you just register to main
>> loop and continue.
>> 
>> This way you have systemd to listen for N sockets (unix, tcp, udp...
>> with the properties and capabilities, as supported by systemd
>> already), it will give you them all in some order. Your app then
>> starts and get these sockets using "sd_*" functions, then you figure
>> out which fd they represent and create the proper ecore_XXX wrapper.
> 
> but you were suggestion we dont use the sd_* stuff and do our own - eg in 
> ecore?
> 
>> Consider the following example: you may have a daemon that may be
>> systemd activated as bellow:
>>   - manually: systemctl start bla.service
>>   - socket: bla.socket that listen to 0.0.0.0:1234
>> for both you have systemd support, but just the second is the socket
>> given to you (you may disable bla.socket and it will still work if you
>> do systemctl start bla.service).
> 
> yeah. sure. but the question is - does adding autofoo checks for systemd
> headers etc. and using them when building e so we can inform systemd we are
> ready... is this what we should do, or implement our own systemd headers for
> such support as part of ecore or whatever? i'm on the fence.
> 
> -- 
> ------------- Codito, ergo sum - "I code, therefore I am" --------------
> The Rasterman (Carsten Haitzler)    ras...@rasterman.com
> 

------------------------------------------------------------------------------
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

Reply via email to