On Wed, Jul 13, 2005 at 10:44:17AM -0500, Chad Walstrom wrote:
> There is very little reason to use the cdbs patchsys-quilt.mk file.
> simple-patchsys works just fine for what you need it to do. Switching
> to a simpler tool will allow you to reduce the version dependency to
> something obtainable on sarge, making backports much easier.
I use quilt to manage patches of several projects. It is true that the
current version of mercurial needs a small patch, so that
simple-patchsys would be enough to handle it. However, this can change
for other versions. And I am not really convince to switch my devel
tools (quilt, simple-patchsys, ...) between my different projets.
> Personally, I try to construct control, build, and maintainer scripts so
> that you can backport one version (the current stable version). There
> is nothing in the mercurial software package that requires unstable
> tools, so why make the packaging process dependent upon unstable?
I use the devel tools I like (quilt). The build dependencies of my
package are the ones required by the current (unstable) cdbs package.
cdbs is used by a lot of packages. Would not it be simpler for you to
first backport sid devel tools such as cdbs ?
Best regards,
Vincent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
