Michael Shields writes: > > Of course I will, but there are at least two cases where I'd want to > override a standard package with a local one: > > 1. I apply a useful patch (original or not) which I want to deploy before > the next Debian release. > > 2. I want to use non-default compile-time settings; for example, to strip > out features for security.
What I've done in this case is to grab the source package, apply the modifications, change the revision to #.carl (eg 3.carl from 3) and do a ./debian.rules binary This gives me a package version between the last and the next, and will give me the new functioanlity. I've found this to be the easiest way to test patches to libc and the like. Now, just install your new .deb file, and keep the mods, so you can apply it to the next source release if necessary. -- Carl Streeter | "Etiquette-wise, there is no proper time [EMAIL PROTECTED] | to use the phrase 'It sucks.'" --Dogbert Just another Perl hacker | "I'm a heartless bastard." --Linus Torvalds Ask me about Debian/GNU Linux. | http://www.cae.wisc.edu/~streeter/
