Hi Jesse, These repos don't all deliver the same things :
~sunab/kdenlive-svn is the original master branch builds, (semi?) automated by Olivier At some point he stopped to update it, as we wrongly understood the users could switch to kubuntu-ci. But he came back and his system goes on... ~kubuntu-ci/* provides updates not only for kdenlive, but also to KF5 libs and many other KDE apps. The problem is that is changes too many things for users interested only in Kdenlive updates. Furthermore they can't follow important bugfixes in MLT / Frei0r as fast as we do. ~vpinon/kdenlive-testing follows the Applications/XX.XX branch (beta then release then rolling bugfix) I did setup this to allow beta or bugfix testing, separate from master (was significantly different around 15.08) (and because Olivier was busy at the time we realized KubuntuCI was not the right answer) (and because I was interested in learning packaging! tweaking dependencies helped me to solve some problems) ~kdenlive/kdenlive-master follows the master branch, to access all the fresh new things This one is built automatically, not on every commit, but when we judge the code is not too broken we just "git push" to the launchpad clone and it starts to compile. This is the setup we would like to keep also for testing (beta) and stable (releases X.Y.Z where Z>0), and as it is owned by a team we can collaborate on it. But I've put this effort on hold, as lauchpad's git import was really new, and I failed to setup branches, not knowing if it was my fault or from the backend... In conclusion : ~kdenlive/kdenlive-master answers (1) (unified team effort) and (2) (automatic build -- not for dependencies), but it does not yet offer all flavors, need to check if branches issue can be solved with some help. Vincent Le lundi 21 mars 2016, 10:50:29 CET Jesse DuBord a écrit : > Hey all, > > Over the past six months, I've noticed around three to four Ubuntu ppa's > for Kdenlive: Olivier Banus', Vincent's, (unofficially) the kdenlive > packages from kubuntu-ci/unstable, and now, recently, the > kdenlive/kdenlive-master ppa. > > (1) Is there a way to unify the efforts and focus on one official ppa > for the Kdenlive product? Would this seem reasonable to do? > > (2) Would their also be a way to automatically build the packages and > their dependencies (like what Vincent seems to be doing, except > manually, for the kdenlive/kdenlive-master ppa)? I think a lot of > support could be given from users if they had easier access to newer > packages with hands-free recurring updates, you know? _______________________________________________ kdenlive mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdenlive
