On Wed, Nov 30, 2016 at 11:38:56PM +0100, Baptiste Jonglez wrote:
1) Would linux-mptcp [1] have its place in [community]? From what I read about linux-zen and linux-grsec [2], there does not seem to be strong objections, especially since most (or even all?) third-party kernel modules now use DKMS.
Hello Baptiste, depends on the votes. As far i can see the package has 9 votes. It's not that much. I would wait for more votes or discuss this with the community if another version of the linux kernel in the official repositories is asked for.
2) Some dependencies of my packages are orphaned in [community], such as msgpack-c [3]. As a TU, I guess it would make sense to adopt them.
Yep, this would make sense.
3) ring-daemon requires non-released versions of restbed [4] and asio [5]. Is it better to wait for upstream to release a version of these libs, or is it acceptable to package a snapshot in [community]?
Baptiste
[1] https://aur.archlinux.org/packages/linux-mptcp/ [2] https://lists.archlinux.org/pipermail/arch-dev-public/2015-July/027311.html [3] https://www.archlinux.org/packages/community/x86_64/msgpack-c/ [4] https://aur.archlinux.org/packages/restbed-latest/ [5] https://aur.archlinux.org/packages/asio-latest/
It is definitly better to wait for a stable upstream release. Please do not push snapshots of git branches in community when you can avoid that. Best regards chris