On Fri, 06 Sep 2013 16:24:35 +0100 Tom Hacohen <[email protected]> said:
> On 06/09/13 16:22, Carsten Haitzler (The Rasterman) wrote: > > On Fri, 06 Sep 2013 14:34:17 +0100 Tom Hacohen <[email protected]> > > said: > > > >> On 06/09/13 14:02, Carsten Haitzler (The Rasterman) wrote: > >>> On Fri, 06 Sep 2013 13:25:24 +0100 Tom Hacohen <[email protected]> > >>> said: > >>> > >>>> 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. > >>>>> > >>>> > >>>> File is indeed from upstream. We had the same discussion at the time (in > >>>> this ML), and decided to just ignore eodev's existence. To be fair, we > >>>> concentrated more about the namespace, and less about the library > >>>> name/pkg-config file name. I don't really mind changing it, the problem > >>>> is change what, and to what extent? > >>>> > >>>> Other people: what do you think about it? > >>> > >>> i'm pretty ambivalent to a rename... just keep it as close to eo.pc as > >>> possible (efl-eo.pc?) > >> > >> I can do that, but is that really what we want? > >> > >> Kinda sucks. :| Also, I wonder about their header names, is it Eo.h as > >> well? Sure, we store it somewhere else on the file-system (eo-1), but > >> that still could be a problem with #include. > > > > no idea. worth looking at. but this means something wants to use both eo AND > > this other lib.. and thats basically likely zero chance... as we put our > > headers inside dirs of our own... but pc's live all in the same dir thus > > have to not conflict. > > Not if they ship their headers to /usr/include/Eo.h or whatever. true. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
