On Fri, Aug 12, 2005 at 10:59:23AM -0300, Henrique de Moraes Holschuh wrote: > On Fri, 12 Aug 2005, Steve Langasek wrote: > > On Fri, Aug 12, 2005 at 01:50:33PM +0200, Daniel Leidert wrote: > > > > Aside from wasting (a little) > > > > space in the archive, that makes it harder for NMUers or passing > > > > developers > > > > to see what's going on in your package.
> > > In this case, you could use dpatch to change things and then it is not > > > harder to see, what is going on. > > No, it just makes it hard to examine the differences between two versions > > using debdiff, rather than making it hard to look at the diff for a single > > version. > Then we have a design problem with debdiff, don't we? Uh, no, it's a design issue with *dpatch*. > Anyway, for users of dpatch-like packaging methods, that is a non-issue. Unless you expect the release team to graciously accept an update to your package during a freeze. > Using Debian-packaged and fixed autotools (*especially* libtool and gettext) > instead of whatever upstream uses is almost always a very good idea in my > experience. Yes, making sure you have the Debian libtool fixes is a very good idea, but that's not the same thing as build-depending on autotools Just Because. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
