http://bugzilla.spamassassin.org/show_bug.cgi?id=3523
------- Additional Comments From [EMAIL PROTECTED] 2004-06-25 18:11 ------- '- The current build is called "Mail-SpamAssassin-x.y-latest" -- ie. contains just the branch version plus some tag. I chose -latest instead of -cvs, -svn or -trunk as its the most neutral in my eyes. I guess we'll have also two -latest ones lying around -- one for HEAD and one for the current stable branch.' Agreed with Duncan -- "-dev" is more appropriate, since it implies instability ;) I don't even think including the branch name is necessary, as I don't want to get into having > 1 "dev version" available on the website. (anyway, "-x.y-dev" isn't appropriate now that we have 3-part version numbers, "-3.0-latest" should be "-3.0.x-latest" or something.) - If some essential command inside the script fails, it actually bails out with an exit code. - I enabled 'set -x' -- pretty useful to see what exactly failed :) +1, both good ideas. - If no gppsign script is found, the release will build successfully, unsigned but print a fat warning in the end.' -1. Could you make that behaviour something that's enabled by an optional commandline flag, or env variable, or something? We don't want the nightly scripts to suddenly stop signing the files, and nobody would notice because the builds scripts carry on fine but the warning message never gets seen. OK, I see one more problem -- why not use "make tardist" and "make zipdist"? I'm not sure I see the benefit of not using those. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
