[Pkg-ime-devel] Bug#750623: Bug#750623: Bug#750623: What is the hold-up of uploadin new package

[GUO Yixuan]

On Sun, Jun 22, 2014 at 08:27:12PM +0900, Osamu Aoki wrote:
> 
> On Sun, Jun 22, 2014 at 01:45:32AM +0800, Aron Xu wrote:
> > On Sun, Jun 22, 2014 at 1:33 AM, GUO Yixuan <culu.gyx at gmail.com> wrote:
> > > I'm just waiting for a confirmation on the librime-dev => librime1-dev
> > > renaming, from Aron, as we discussed in a previous thread. [1]
> > >
> > 
> > As said before, I don't have strong opinion on either way.
> 
> My popsition is that you have not presented enough reason to do this.
> So do not do this.

I remember one possible reason: librime 1.0 breaks some ABI and API
compatibility, so we should change the -dev package name. [1][2]

quote form ChangeLog:
 15 2013-11-10  GONG Chen  <chen.sst at gmail.com>
 16 
 17         * rime_api: version 1.0 breaks ABI compatiblility.
 18 
 19         the minimum changes in code required to migrate from rime 0.9 api is
 20         to initialize RimeTraits with either RIME_STRUCT or RIME_STRUCT_INIT macro.
 21 
 22         while source code compatibility is largely maintained with the exception
 23         of the aforementioned RimeTraits structure, rime 1.0 introduces a version
 24         controlled RimeApi structure which provides all the api functions.

[1] https://wiki.debian.org/TransitionBestPractices
[2] http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#sonameapiabi

> > > In addition, because the symbol files are not useful, should we create
> > > a shlibs file?
> > >
> > > [1] https://lists.alioth.debian.org/pipermail/pkg-ime-devel/2014-May/004168.html
> > >
> > 
> > Don't think it's so useful nowadays, either use symbols or don't use
> > anything in normal cases.
> 
> Hmmm... I think if we drop the symbol file, packaging tool chain
> automatically generates the shlibs file.   Please look into your
> generated binary package to verify :-)  I see it there.
> 
> I suggest you to add the following at the top of debian/rules file if
> you have not.  I am doing this for all my new upload (see ibus).
> 
> # See dpkg-buildflags(1)
> DPKG_EXPORT_BUILDFLAGS = 1
> include /usr/share/dpkg/default.mk
> #export DEB_BUILD_MAINT_OPTIONS = hardening=+all
> export DEB_CFLAGS_MAINT_APPEND  = -Wall -pedantic
> export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
> 
> This also helps you to test build consistently etc.  This is good idea
> for the newer dpkg(>1.16.1).
> 
> See explantion in the EXAMPLES section of dpkg-buildflags(1) manpage.

Thank you! I'll check it out.

Cheers,

Yixuan