Carsten Haitzler (The Rasterman) <ras...@rasterman.com> writes:

> the rationale is that micro versions do not have anything change in a header
> that would affect compatibility forwards or backwards. we shouldnt be adding
> features in micro releases (adding enums, struct members, functions etc.). 
> thus
> there is no need at compile time to know this as it is simply a matter of bug
> fixes.
>
> minor version releases we add funcs, features etc. THUS there is a need to
> #ifdef use of new features *IF* the version is right.

Hmm, OK. Right now I guess it's probably fine to depend on major and
minor versions only, IIRC the last time we relied on a specific SVN
revision for a new feature was a few years ago.

> i don't get why you can't use pkg-config?

I've been trying to rely less on it from CMake; for one, it might not
even be installed if the user has installed all WebKit dependencies from
binary packages, plus we already detect library and include paths with
CMake itself to get absolute paths instead of the '-lfoo's provided by
pkg-config. So being able to easily get the current library version
would be the last part of the puzzle for using pkg-config only if it is
available.

> a reason NOT to do micro version #defines in headers is that they are all
> (except elm) manually changed and thus that increases the burden of adjusting
> all of these per micro AND minor version release. right now its only per 
> minor.
> to automate it we'd have to make all these headers Header.h.in and i just 
> didnt
> want to go thru all of efl to do this.

Well, it's good to know that the primary reason seems to be
maintenance-related since that's easy to fix. Would patches to change
that in the libraries that are part of the release cycle be accepted?


------------------------------------------------------------------------------
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

Reply via email to