On Tue, Aug 17, 2010 at 6:17 PM, Tom Hacohen
wrote:
> On Tue, 2010-08-17 at 18:13 +0200, Vincent Torri wrote:
>> To be consistent with the other EFL, we would move all the content of
>> src/include in src/lib. I'm not against that.
>
> Exactly what I said in IRC :)
> If we decide to do that, we ne
On Tue, 2010-08-17 at 18:13 +0200, Vincent Torri wrote:
> To be consistent with the other EFL, we would move all the content of
> src/include in src/lib. I'm not against that.
Exactly what I said in IRC :)
If we decide to do that, we need to do it before the release.
Actually, I think it's bette
On Tue, 17 Aug 2010, Tom Hacohen wrote:
> Hey all,
>
> I have heard today that in Eina, all the .h's and .x's should be located
> in the "src/include" dir, even if they are *not* shipped.
>
> That's ugly, stupid and confusing.
>
> There's no reason why to put headers or include files that should
Hey all,
I have heard today that in Eina, all the .h's and .x's should be located
in the "src/include" dir, even if they are *not* shipped.
That's ugly, stupid and confusing.
There's no reason why to put headers or include files that should not be
shipped in that directory for the following reas
