So far, modules such as eina, evas and friends only define their major
and minor versions on public headers such as Evas.h.
While this is OK most of the time, one might also need to check the
micro version as well -- my current use case is performing version
checks without having to rely on pkg-config on WebKit-EFL, but others
may have other uses for that as well.
The current way of doing that would be building a program that got those
version numbers from the {edje,evas,etc}_version variable, which is
needlessly complicated when one already has half of the version
information written in the headers.
Is there a rationale for not exposing all version information in .h's or
can I work on a patch for that?
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
