Hi Andreas, > Either this or we use common VCS. Please tick-mark your prefered option > > [ ] I'll add you to Debian Med team and you commit to SVN > [ ] I'll add you to Debian Med team and migrate the package to Git > [ ] I move the package to collab-maint Git > [ ] I move the package to collab-maint SVN > > I'd trust your insight as a "real" consumer of this package to evaluate > the status of the development snapshot - so yes, it would be OK to > base the packaging on this version. This would mean a move to Git in > any case to enable us working on the very same upstream tarball.
Thank you for your trust in me. But I'm really new on debian development. At the beginning, my motivation was to bring the tomahawk player into the debian souces. And so I started to maintain the missing dependences for it. Tomahawk and its dependences uses cmake and so I'm very familiar with cmake and debian packaging. I've adopt the debian/rules structure of the libquazip package and modified it to use cmake instead of qmake. Now, the packages libechonest, liblastfm, libjdns and libjreen are available in Qt4 and Qt5. I think the best way would be: [X] I'll add you to Debian Med team and migrate the package to Git But I'm not so familiar with using VCS. I would be very happy if you could supports me. Stefan