On Sat, Nov 05, 2005 at 12:17:29AM +0100, Henning Makholm wrote: > Scripsit Steve Langasek <vorlon@debian.org> > > If you're interested in making this happen I'll be happy to give > > you any info I can; > 2) Any advice on how to test patches to ftp-master code before > submitting them? My own scripts I can dry-run by substituting a > dummy command for sendmail and run them in the very place where > they will eventually function. In contrast, construcing a test > mock-up of the ftp-master environment to do test runs of a patched > britney appears to be highly nontrivial. Does some automation for > this purpose exist? Or what do ftpmaster/release gurus do when you > change code? Heh, so I guess the only info I can offer you is to say that no, there's no particularly useful automation for this... creating a copy of the ftp-master env is non-trivial, yes, but it's also the only real option, AFAIK. :) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature