On Sun, Aug 15, 2010 at 09:16:26AM +0200, Reinhard Tartler wrote:
On Sun, Aug 15, 2010 at 02:23:59 (CEST), Felipe Sateler wrote:

On 14/08/10 11:08, Reinhard Tartler wrote:
On Sat, Aug 14, 2010 at 16:19:27 (CEST), Felipe Sateler wrote:

On 14/08/10 06:13, Reinhard Tartler wrote:
debhelper maintains a history of very stable interfaces, called compat levels. I'd really love to see something similar to cdbs. And this very strict commitment to stable interfaces and semantics help a lot for backporting packages.

How does maintaining several API versions (compat levels) help backporting?

You can pretty much rely on the exact behavior of debhelper commands. future improvements and addition are still possible at higher levels, but for the sake of compatibility, they are not used until you bump the debhelper compat level.

But that is forward-porting, not backporting.

if you always use the most recent debhelper compat level, then yes. If you leave your package at the highest compat level that is in the oldest release you care about, then it helps backporting.

for stable this would mean to avoid the short form 'dh' forms with the quilt series features.

Do I understand you correctly here in that you really are not talking about the ABI levels at all, but minor version numbers of debhelper?

Or do you suggest to stick to debhelper compat level 6 for now, to not accidentally use features introduced in e.g. 7.2?

Or do you somehow mean to say that the fine ABI handling of debhelper also cover the changes between 7.0 and 7.2?

Kind regards,

 - Jonas

 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: Digital signature

pkg-multimedia-maintainers mailing list

Reply via email to