Hi ML, it has been asked to me a few times why I removed changelog.in from configure.in, since that way "the versioning was automatic".
That's in fact the real problem. Let me explain myself: If the version of eet (for example) is always the same (0.9.10.023), apt-get will never update the packages from the repository, unless eet reaches a new version. To correctly maintain a debian repository with cvs software, I need to have packages version like (in eet example) 0.9.10.023+cvsYYYYMMDD. I can't add the cvs date in the version while configure (launched by debuild script) replaces the version each time I run it. Another example of this problem is the Enlightenment package. The CVS version of Enlightenment is 0.16.999, but the version present in Debian is 1:0.16.7.2, which is superior $ dpkg --compare-versions 0.16.999 '>' 1:0.16.7.2; echo $? 1 $ This way, when a user upgrades his system, E17 is replaced by E16, and that's not what we want. A manual handling of the debian version allows to add epochs (1:) and cvs suffixes, which make the packages usable without any problems. I decided to do this since when I created my own debian repository (before joining the development team) i did all these changes one by one in all the source directories before being able to build up a functional repository. I hope this explanation will clarify the purpose of my actions to those who were wondering. I am here for any further doubts - xstasi ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
