[Pkg-ime-devel] brise: package renaming?
aron at debian.org
Sun Jun 8 00:29:11 UTC 2014
On Mon, Jun 2, 2014 at 6:52 AM, GUO Yixuan <culu.gyx at gmail.com> wrote:
> On Mon, Jun 02, 2014 at 06:20:33AM +0800, Aron Xu wrote:
>> On Thu, May 15, 2014 at 2:15 AM, Guo Yixuan <culu.gyx at gmail.com> wrote:
>> > Hello,
>> > In version 0.30, several files were replaced with their updated version,
>> > under different names.
>> > commit c17cd96 (tag: upstream/0.30, 1n1b/upstream)
>> > Author: Guo Yixuan <culu.gyx at gmail.com>
>> > Date: Sun May 11 18:30:11 2014 -0400
>> > Imported Upstream version 0.30
>> > delete mode 100644 extra/stroke5.dict.yaml
>> > delete mode 100644 extra/stroke5.schema.yaml
>> > create mode 100644 preset/bopomofo_tw.schema.yaml
>> > create mode 100644 preset/stroke.dict.yaml
>> > create mode 100644 preset/stroke.schema.yaml
>> > create mode 100644 supplement/sampheng.schema.yaml
>> > delete mode 100644 supplement/stroke_simp.dict.yaml
>> > delete mode 100644 supplement/stroke_simp.schema.yaml
>> > delete mode 100644 supplement/triungkox3p.dict.yaml
>> > delete mode 100644 supplement/triungkox3p.schema.yaml
>> > I renamed the Debian packages accordingly . Is this OK? If so, do we
>> > need to declare conflicts + replace + provide in debian/control?
>> I have no strong opinion on this, and if you are changing the package
>> names, you need to handle the package transition.
> OK. In this case, the new packages don't have filename conflicts
> with the old packages, so I'm going to add Provides, but without
> Breaks/Conflicts/Replaces. I'll also add a NEWS.Debian to inform
> the users of this change, so they can adjust their config files
I doubt the usefulness of a NEWS.Debian a little bit, it's a simple
package transition without affecting usability anyway.
More information about the Pkg-ime-devel