On Mon, 14 Feb 2011 15:14:13 +0100 Cedric BAIL said:
absolutely right. we CANT break the api. can't change so any existing app or
code would break. that is the price of stability and the 1.0 release everyone
has been screaming for for so long. now we've made our bed - we have to lay in
it. too ba
On Mon, Feb 14, 2011 at 3:04 PM, Andrey Riabushenko wrote:
>> Well, I don't see how you could remove eet cipher and signature
>> functionnality without impacting eet internals.
> Change is inevitable and imminent :) Though, It can wait for EFL 2.x
> branch opening for API changing commits.
You w
Hi,
>
> Well, I don't see how you could remove eet cipher and signature
> functionnality without impacting eet internals.
Change is inevitable and imminent :) Though, It can wait for EFL 2.x
branch opening for API changing commits.
>Signature need to manipulate the internal data of the map
Hi,
On Sun, Feb 13, 2011 at 4:15 PM, Andrey Riabushenko wrote:
> I have been looking for ways to make EFL even more compact than it
> is currently. One thing I have noticed about eet that it has many
> dependencies:
>
> #ldd libeet.so
> linux-vdso.so.1 => (0x7fff655ff000)
> lib
Hi everyone,
I have been looking for ways to make EFL even more compact than it
is currently. One thing I have noticed about eet that it has many
dependencies:
#ldd libeet.so
linux-vdso.so.1 => (0x7fff655ff000)
libgnutls.so.26 => /usr/lib/libgnutls.so.26 (0x7f6b2656b000)
