Hi Henrique, On Mon, 24 Jan 2011, Henrique de Moraes Holschuh wrote: > No. When we backport something, we are perfectly capable of backporting > dpkg-dev first.
> Crap happens when you need backported debhelper, should whomever did that > backport have neglected to _change_ debhelper to do whatever is really > needed in the older distro. > This is not the sort of problem that backported dpkg-dev would ever cause. probably you are right... but we do not know for sure. dpkg-dev is the core component, and went from 1.14. series to 1.15 from lenny to squeeze... noone backported it, nor gettext (its build-dependency) so we do not know for sure if backported version could not lead to some interesting side-effects. thus I thought that making few leaf packages friendlier to older versions of dpkg-dev would be easier, than taking care about correct backporting of the core components > Most of the time, all we backport-lovers really need is complete (and > properly versioned) build dependencies. It _does_ help if you stick > to debhelper and ucf functionality available on stable for packages > that are extremely likely to be backported, though. well -- I can only agree with that ;-) -- =------------------------------------------------------------------= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110124173911.gp8...@onerussian.com
