[Pkg-alsa-devel] 1.0.11rc3

[Jordi Mallach]

Hello,

On Mon, Feb 06, 2006 at 11:13:43AM +0100, Thomas Hood wrote:
> OK, I removed the debian/compat files, reverted changes to debhelper
> Build-Dependencies and updated changelogs.
> 
> In the past I thought that the debhelper compatibility level should
> always be set and that debhelper would support all levels forever.
> However, we now learn that old compatibility levels will get abandoned
> after a while (levels 3 and below are going to disappear, according to
> lintian); so it seems best not to specify a compatibility level and
> just use the default (currently level 5).  If a backward-incompatible
> change is ever made that affects one or more of our packages then we
> can introduce a compatibility level setting at that time in order to
> work around the problem.

Well, both points of view are valid: if you set your compat level to
something fixed, you know how debhelper is going to behave, always,
until the version you're using dissapears from unstable.

In general, when that happens, it's common that you have moved at least
two levels forward, though.

If you just follow the default, yes, you'll be using what debhelper
recommends, but you might be getting ftbfs or other kind of bugs because
a change in debhelper.

I think it's very common in Debian to use debian/compat, though. I have
no problems with using no compatibility until it affects us in some
strange way.

Jordi
-- 
Jordi Mallach Pérez  --  Debian developer     http://www.debian.org/
jordi at sindominio.net     jordi at debian.org     http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-alsa-devel/attachments/20060206/aad58b80/attachment.pgp