If you want to distribute updated packages for more distributions, this service could be better than Launchpad/PPA:
build.opensuse.org I maintain peinddd old&new preinstallation profiles for Debian and Ubuntu, and those profiles for Ubuntu point to: deb http://ppa.launchpad.net/sunab/ppa/ubuntu intrepid main #u8.10 deb http://ppa.launchpad.net/sunab/ppa/ubuntu jaunty main #u9.04 deb http://ppa.launchpad.net/sunab/ppa/ubuntu karmic main #u9.10 deb http://ppa.launchpad.net/sunab/kdenlive-release/ubuntu lucid main #u10.04 deb http://ppa.launchpad.net/sunab/kdenlive-release/ubuntu maverick main #u10.10 deb http://ppa.launchpad.net/sunab/kdenlive-release/ubuntu natty main #u11.04 deb http://ppa.launchpad.net/sunab/kdenlive-release/ubuntu oneiric main #u11.10 deb http://ppa.launchpad.net/sunab/kdenlive-release/ubuntu precise main #u12.04 deb http://ppa.launchpad.net/sunab/kdenlive-release/ubuntu quantal main #u12.10 deb http://ppa.launchpad.net/sunab/kdenlive-release/ubuntu raring main #u13.04 [u13.10 not to Sunab] deb http://ppa.launchpad.net/sunab/kdenlive-release/ubuntu trusty main #u14.04 [u14.10 not to Sunab] deb http://ppa.launchpad.net/sunab/kdenlive-release/ubuntu vivid main #u15.04 deb http://ppa.launchpad.net/sunab/kdenlive-release/ubuntu vivid main #u15.10 El 24/03/16 a les 00:20, Vincent Pinon ha escrit: > Hello, > > This mail maid me to go back to look at lauchpad's git integration... > and it is now actually possible & easy to work directly with the git branches > to package each of them! > So now we have auto builds for: > > ppa:kdenlive/kdenlive-stable -> 15.12 (will be upgraded on 16.04.1 release) > ppa:kdenlive/kdenlive-testing -> 16.04 > ppa:kdenlive/kdenlive-master -> master > > However, MLT (+frei0r) is still uploaded manually (maybe we should setup a > lauchpad git clone?), > and FFmpeg is still the original one from distribution (I always fear to mess > up the other apps like numerous videos players etc). > > I deleted my own PPA as it is now obsolete. Sunab's still might be useful as > it ships binaries for utopic/vivid? > > Let's spread the word on website / docs / forum / other channels? > > Vincent. > > PS: debian/ubuntu packagers are welcome to pick, comment & improve my > packaging, we may work together with git on launchpad or alioth? > (I added important dependencies from forum feedback, but maybe screwed other > things?) > > PPS: I would be glad to see equivalent for other distros; I believe it is > already available for OpenSUSE & Arch or am I wrong? > I don't have anything non-deb installed, but if I can help don't hesitate to > ask (eg: picking evolving dependencies) > > PPPS: anyone working on the code has to push to the lauchpad clone in > addition to the KDE repository after commit to a branch. > An automatic hook can be configured, but no tip for today :-\ > > Le lundi 21 mars 2016, 23:34:17 CET Vincent Pinon a écrit : >> 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 >> kdenlive@kde.org >> https://mail.kde.org/mailman/listinfo/kdenlive >> > > > _______________________________________________ > kdenlive mailing list > kdenlive@kde.org > https://mail.kde.org/mailman/listinfo/kdenlive > _______________________________________________ kdenlive mailing list kdenlive@kde.org https://mail.kde.org/mailman/listinfo/kdenlive
