On 18 November 2014 15:05, Scott Kitterman <deb...@kitterman.com> wrote: > > I'd suggest not just replacing it. How about call your package python- > mysqlclient (as you had originally intended I believe) and have it conflict > with python-mysqldb (since they both provide the same interface, conflicts > is > appropriate). Maintainers can decide which they prefer and if we get a > strong > consensus for Stretch, then we can remove python-mysqldb and have python- > mysqlclient provide it. >
I could do this. However I thought that having two packages that do the exactly the same thing conflict with each other would be frowned upon. (not to mention that the name goes against the policy of calling packages python-modulename). -- Brian May <br...@microcomaustralia.com.au>
