Joachim Wieland wrote: > On Fri, Jan 05, 2007 at 05:55:45PM -0500, Bruce Momjian wrote: > > > The idea of having to do this at every version number bump is pretty > > > unappetizing. Shouldn't we fix things so that the version number > > > doesn't appear in the ecpg regression files? > > > It would be nice, yea, or we can stip out that line when doing the diff. > > Attached is a patch that adds a --regression option to ecpg. I replaced the > manual checking for long options (--version and --help) by a call to > getopt_long(). Unfortunately I don't have access to a platform that does not > support getopt_long, so maybe there is something missing for those platforms > (including for Windows maybe). > > The other patch is against the expected/ directory to replace the version > number with a fixed string.
I have added a checklist item to update the ecpg regression output for major release bumps. I think that is the easiest solution at this point. -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
