On Wed, Nov 09, 2005 at 11:30:23PM +0100, Erik Schanze wrote: > Hi Daniel, > > Daniel Baumann <[EMAIL PROTECTED]>: > > Erik Schanze wrote: > > > Your way will not fail, but could be improved. > > > The advantage of Build-Depends on autotools-dev is to have the > > > newest config.* stuff available. There is no need to include the > > > new config.* files into diff. If you do so, you don't need to > > > Build-Depend on autotools-dev, but your diff grows. > > > > Well, I beg to differ. Its important to have current > > config.{sub,guess} to ensure, that the package builds on the latest > > debian ports (e.g. kfreebsd), and sometimes.. if the files are really > > outdated, its even essential to be buildable on !i386. > > > Yes, it's important to have the latest config.* files at build time, but > isn't the autotools-dev depends responsible for it, that they are > available under /usr/share/misc/ at buildtime? > Then we link to it and have it. The original ones are out of interest. > (Should be moved aside.) > Why should the config.* files included into the diff? > Aren't autotools-dev available on ports you mention? I think the idea is that then the .diff defines the entire state of the package as it existed when the maintainer created the .deb for his architecture.
-- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]