On Sun, Jul 25, 2010 at 11:38 AM, Chris Frey <cdf...@foursquare.net> wrote: > On Sun, Jul 25, 2010 at 11:11:55AM +0200, Jose Carlos Garcia Sogo wrote: >> If there is an API change, first the soname of the library should be >> bumped (that's upstream labor) so the package should move from >> libbarry0 to libbarry1. > > Yes, this is the way it will be done once we release a version 1.0. > But until then, the 0.x version stream of Barry is considered "development" > and the API can and does change at will, with no soname version changes. > > See doc/VersionNotes for the plan for verion 1.0, when that day comes.
Ok, but the main problem is that usually a lot of people use the software long before that 1.0 version is released, and reaching to it takes ages, so not changing soname makes packaging much more difficult. > > >> Also, barry-util should depend on a tighest >> version of libbarry. You should have made barry-util depend on at >> least first version of libbarry 0.16 (I don't know if it is done yet). >> This way, apt will update barry-util at the same time libbarry is >> updated. > > This is a good point.. we should double check our debian version dependencies. > I didn't think it was possible to have 0.15 and 0.16 installed at the > same time, but if it is, I agree it is a bug in the binary packaging. No, it is not if you don't change soname, so version 0.15 is libbarry0 and version 0.16 is libbarry1. Also, if you want them to be fully installable at the same time, you should also have a libbarry0-dev and libbarry1-dev instead of plain libbarry-dev, but this would only affect people developing or building packages. If there is only libbarry0, any new version will overwritte currently installed one. But here is were the problem arises. If the user only updates libbarry0 (by apt-get install libbarry0), he won't update barry-util, because the barry util dependecy says that it is compatible with > 0.15, so version 0.16 matches this as well. That's why barry-util dependency in libbarry0 has to be updated to >0.16. This way apt-get will know that when updating libbarry0, current barry-util doesn't have its dependencies satisfied, and must be updated as well. Clear? It is easier to understand than to explain I think! -- José Carlos García Sogo jcs...@gmail.com ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
