On Tue, Mar 25, 2008 at 10:30 AM, Bernd Jendrissek < [EMAIL PROTECTED]> wrote:
> On Sun, Mar 23, 2008 at 7:27 AM, John Calcote <[EMAIL PROTECTED]> > wrote: > > > Thanks, but the problem with this solution is that I would have to > > > rerun the .configure step each time. Forgetting to do that is as as > > > easy as forgetting to edit the spec file. > > How do you know that you've committed all your local changes before > typing 'make'? At my previous job I made that mistake so often that > in the end I resorted to brute force: I added calls to "cvs stat" and > "cvs diff -Nup" to the script that made the release ZIP archives. > > > Don't take this wrong - I totally believe you. But, I'm trying to > figure > > out why this has never been a problem for me. > > Maybe it's idiosyncratic and you're immune to this particular act of > forgetfulness? No, I'm the idiot, mostly. I have a check in the .pl file that detects a missing commit and prints a warning. Sure, then I have to rerun the make after the commit, but before this I might not realize I hadn't updated the spec file which could lead me to generate an rpm that didn't reflect the right source. I hope that makes sense. Thanks, Jim.
