Hi, On Thu, Jul 3, 2014 at 8:12 AM, Osamu Aoki <osamu_aoki_h...@nifty.com> wrote: > On Wed, Jul 02, 2014 at 07:56:49PM +0200, Emilio Pozuelo Monfort wrote: > > > The renaming is due to a backward-incompatible API change in > > > librime 1.0, where some struct members changed types. So I > > > followed the recommendation here.[1] > > > > > > [1] https://wiki.debian.org/TransitionBestPractices > > > > That advice is wrong. Renaming the -dev package makes sense if you're going to > > keep the two versions of the library for a while, e.g. libgtk2.0-dev and > > libgtk-3-dev, which usually means you renamed the source package (gtk+2.0 and > > gtk+3.0 in my example). In your case, you want to keep the same librime-dev > > package name. Can you change it back? > > > > I will review and edit that wiki page, thanks for the link. > > Very good. That is my thought but there was no external resource > backing it. > > Havoc has interesting post on multi dev library case as below, > > Jere is what I wrote previously ... > > I do agree to use the versioned -dev when these 2 -dev package are made > > to be co-installable and useful in such shape. This happens with major > > This practically means source package with different name. > > > libraries. For this, it require us to do more than bumping number in > > -dev package name. See example: > > http://ometer.com/parallel.html > > (HP used to work at R-H and used to be with Debian as I understand)
Thank you for this reference. As I understand, our current advice should be: you never need to change the name of the -dev package, as long as the source package name is not changed. Is this correct? > I will upload new git head when prompted. Is it ready? Yes, it is. (I just noticed you already uploaded it. Thanks a lot!) Yixuan
