Hello. On 19/10/15 21:52, Ponomarenko Andrey wrote: > Hello, > > I noticed that you maintain binary compatibility of the EFL and Elementary > here: https://devs.enlightenment.org/~tasn/abi/ > > Recently I've started to maintain it too on my personal web-page: > http://abi-laboratory.pro/tracker/timeline/efl/
Interesting. Thanks for bringing this to our attention. I add it to my list of things to have a look at. > The source code of the ABI tracker is open and you can set up it locally on > your site along with the old tracker. It's also based on the > abi-compliance-checker tool, but doesn't require compilation of header files. > It uses DWARF debug info from shared objects instead. > We have two things (out of my head) that we would like to behave differently with what we currently have. 1) Having a list with all new API symbols in a simple text file would be great as we could use that to attach it to the NEWS file, check for unit tests, etc 2) As you can see in your analysis we have soem symbol removals from time to time. These are in API we do not consider stable and are only available behind a beta define for applications. Having a way to sort out such beta API is something we also miss. Not sure if your tool is more flexible here. regards Stefan Schmidt ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
