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