Le 09/09/2013 15:43, Tom Hacohen a écrit :
> On 03/09/13 22:25, Côme BERNIGAUD wrote:
>> Hello,
>>
>> I saw that there is a new component named EO in the EFLs.
>> EO is already a library, it stands for «Evolving Objects» :
>> http://eodev.sourceforge.net/
>>
>> This is causing trouble, at least for one file:
>> /usr/lib/pkgconfig/eo.pc is the pkgconfig for evolving objects, which is
>> already used by several projects over the past years.
>>
>> So it might be a good thing if you could rename at least this file.
>>
>> Côme
>>
>> PS: The problem was found when trying to install the AUR package efl-git
>> on ArchLinux, but I'm pretty sure this file is from upstream.
>
> Unfortunately it's really annoying to change it. After discussing it 
> on IRC and thinking about all the pain involved, we decided not to 
> change anything.
>
> We don't want to change the library name itself, that is, we like eo. 
> Changing just the pc file creates a lot of issues with our build 
> system which does a lot of things automatically and assumes a specific 
> template to be followed.
> libXX.so, XX.pc and etc.
That is a very sad decision. It means people won't be able to install 
both EO and the EFL…
The filename eo.pc was already used since several years by EO, it's 
childish to just ignore that and take the same name.
You should indeed use a pattern like efl/xx.pc or efl_xx.pc because if 
you intend to keep using two-letters names, you'll find a lot of them 
are already in use.

Someone was also anxious about eo.h names or such, I just checked, and 
libeo is also using:
/usr/include/eo     folder
/usr/share/eo       folder
/usr/lib/libeo.a       file
/usr/lib/libeo.so     file

Which might also conflict with your EO thing (I did not check, just 
thought these files might conflict)
>
> -- 
> Tom.
Côme

------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to