You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the article How do I patch a Debian package:

#6 Re: How do I patch a Debian package Posted by undefined (192.91.xx.xx) on Mon 26 Sep 2005 at 22:23 somebody mentioned dpatch, but unless the debian maintainer has already added the framework to the package, or you intend to maintain this package (adding & removing patches yourself), dpatch is too much overhead for a single patch. but if you do it, please send a patch to the debian maintainer; they may appreciate it. but i really must recommend pbuilder if you do much building of packages (whether one package multiple times or several packages). i use pbuilder to build/backport packages on my testing desktop for my stable server. works great even for building software that you are not going to package, but just going to tarball: build, install, & tarball it in the pbuilder chroot, then untar it on the server. i use a chroot because i usually have to muck with the configure or make files to get everything to install properly under /usr/local and i don't like doing this trial & error process on my server. sure, a plain chroot is all that's needed, not pbuilder's, but if you are already using pbuilder for building debian packages, might as well use pbuilder for this too.

Inappropriate comments will be removed.

Username:

Password:

[ Advanced Login ]

Register Account