We don't want the ability to cross-pollinate code with those projects
and they are SEPARATE PROJECTS. The goal of eina was to unify around
one shared data lib, so why would we not be using eina?

On Wed, Aug 6, 2008 at 3:09 PM, Gustavo Sverzut Barbieri
<[EMAIL PROTECTED]> wrote:
> On Wed, Aug 6, 2008 at 5:04 PM, Nick Hughart <[EMAIL PROTECTED]> wrote:
>> Gustavo Sverzut Barbieri wrote:
>>>
>>> On Wed, Aug 6, 2008 at 4:53 PM, Nick Hughart <[EMAIL PROTECTED]> wrote:
>>>
>>>>
>>>> Gustavo Sverzut Barbieri wrote:
>>>>
>>>>>
>>>>> On Wed, Aug 6, 2008 at 4:07 PM, Nick Hughart <[EMAIL PROTECTED]> wrote:
>>>>>
>>>>>
>>>>>>
>>>>>> Have fun getting any of the libs in CVS to use Eina now.  Just more
>>>>>> split effort...
>>>>>>
>>>>>>
>>>>>
>>>>> Since they're basically the only doing any code in CVS, it will be as
>>>>> hard as before.
>>>>>
>>>>>
>>>>
>>>> I guess I should stop working on EFM then and all those working on EWL
>>>> should cease as well.  Don't make stupid statements.  There are plenty of
>>>> people who have and continue to contribute when they can to all of E's
>>>> CVS,
>>>> by making such a statement you just look stupid.  I realize you are
>>>> trying
>>>> to make a point with all this switching, but in all honesty all it's
>>>> going
>>>> to do is make things worse, so thank all of you for screwing up our
>>>> community more then it already was.
>>>>
>>>
>>> Ok, so let's reduce the scope of my statement to make it less stupid:
>>> "Since they're basically the only doing any code in CVS [THAT WOULD
>>> USE EINA DIRECTLY], it will be as hard as before".
>>>
>>> I see ecore and evas as main users, possible provide some helpers to
>>> have eet descriptors with eina data types. Of course there are many
>>> places where it could be used, including EWL or ETK, but I saw no talk
>>> about moving them so far.
>>>
>>
>> EWL uses ecore data types, thus it will use eina indirectly and thus
>> indirectly it will be bound by the terms of the LGPL as will anyone using
>> ecore, evas, edje, etc.
>
> ah, fine... so you all use BSD's libC, do not use GNU LibC or any
> other LGPL library...
>
> --
> Gustavo Sverzut Barbieri
> http://profusion.mobi embedded systems
> --------------------------------------
> MSN: [EMAIL PROTECTED]
> Skype: gsbarbieri
> Mobile: +55 (19) 9225-2202
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> enlightenment-devel mailing list
> enlightenment-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to