On 8/2/19 6:29 PM, Simon McVittie wrote: > On Mon, 08 Jul 2019 at 11:48:17 +0700, Arnaud Rebillout wrote: >> I'd like to package mutest for Debian. Is the GNOME packaging team >> interested in this package, can I maintain it with the team? > graphene already uses a bundled copy of mutest, so it would seem > appropriate to maintain the unbundled version in the GNOME team too. > > However, at the moment mutest is explicitly not stable: > > **WARNING**: µTest's API is still in flux! > > so I don't think it would be appropriate for packages like Graphene > to use a system copy at this stage. The documentation says: > > The preferred way to use µTest is to include it in your own projects > using a Git sub-module, and then building µTest as a static library. > > which I think meets the "unless the included package is explicitly > intended to be used in this way" criterion in Policy §4.13.
Alright, then maybe better wait for a release of mutest, no need to review my packaging now. There's no rush. I will ping again on this mailing list when mutest releases a version, and my packaging is ready. >> What's the preferred way, should I go through the Debian mentors page, >> or simply using Salsa is enough? > I would personally prefer Salsa. Me as well, perfect. > >> - I asked for access to the gnome team on salsa, my user is `arnaudr-guest` > Someone on the Owners list will have to do this; but if nobody gets round > to it, I can create an empty mutest project and give you access to it, > and you can work that way? Sounds good to me, thanks! Arnaud
