On Wed, Dec 17, 2008 at 11:49 PM, opensourcecat <[email protected]> wrote: > On giovedì 18 dicembre 2008 08:43:12 Jean-Michel Pouré wrote: >> The idea of unstable releases is good. We don't really need releases in >> this situation, as we will only use SVN. Maybe mlt needs a special svn >> tag, like libmlt.so.svn. We can suppose that .svn is always the latest >> version. > > Sounds good. This is up to Dan at this point. If he can do it easily packagers > will be facilitated in creating frequent -unstable packages
I looked into this, and it will be easy to do. Right now, soversion=1 in configure, right next to where I set version=0.3.3. After 0.3.4 is release, I will set soversion=1head. This will let it still keep a version check on unstable, i.e. 1head != 2head. This will create in lib/ : libmlt.so.0.3.4 libmlt.so.1head -> libmlt.so.0.3.4 libmlt.so -> libmlt.so.0.3.4 whereas the stable version will have: libmlt.so.1 -> libmlt.so.0.3.4 I want to do this after the next release because it is soon, and I don't want to change the soversion on everyone who is tracking HEAD at the moment during final testing. Cool? -- +-DRD-+ ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Kdenlive-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kdenlive-devel
