[Pkg-vala-maintainers] [Pkg-ime-devel] Bug#675657: libskk: Please switch to vala 0.16

Osamu Aoki osamu at debian.org
Sun Jun 3 03:03:42 UTC 2012


Hi,

I saw following bug report and wondering why this is not handled
semi-automatically.

On Sat, Jun 02, 2012 at 06:03:58PM +0200, biebl at debian.org wrote:
> Source: libskk
> Version: 0.0.12-2
> Severity: normal
> User: pkg-vala-maintainers at lists.alioth.debian.org
> Usertags: vala-0.16-default
> 
> Hi,
> 
> libskk currently has a build dependency on either valac-0.14 or
> libvala-0.14-dev.
> 
> For wheezy, the default valac version will be 0.16 and we recommend
> that you switch libskk to valac-0.16.
> 
> That said, as the default was switched rather late to 0.16 during the
> release cycle, we will ship both 0.14 and 0.16 for wheezy.
> 
> This means your package will remain buildable in any case, but if you
> are planning an upload anyway, please consider switching to 0.16
> while at it. In most cases a simple update of the build dependencies
> is sufficient.

My question is why people write explicitly versioned build dependency.

Instead of "Build-Depends: valac-0.16 (>= 0.16.0), libvala-0.16-dev (>= 0.16.0)",
why not to use: "Build-Depends: valac, libvala-dev"?

You already provide valac. Why not provide libvala-dev pointing to
libvala-0.16-dev?  Then you could have dealt this via binNMU.  Of course
if there is major non-compatible changes happen, we could chose to
change name of virtual package (Something like python to python3).

Vala seems to be fast changing with mostly forward compatible feature
additions, this seems to be viable option.  I may be totally wrong on
understanding of vala situation though....

Just my thoughts....

Osamu





More information about the Pkg-vala-maintainers mailing list