Snapshot, diffs and crap

Jeffrey A Law law@cygnus.com
Wed Jan 28 09:32:00 GMT 1998


  In message < 199801281706.SAA05624@quatramaran.ens.fr >you write:
  > Related to the .brik problem, I don't quite understand how such a problem
  > could sneak in... 
The way we created the .brik file was to list all the args on the
command line.

The old box which had the cvs repository and where we made snapshots
from allowed a much larger arg block than the new box.

In an attempt to fix it when moving snapshots to the new machine I
botched the script.


  > I would have thought snapshot-building were designed to
  > enforce consistency. That is: build a new snapshot archive.
  > Unarchive old and new snapshot. Compute corresponding diff file.
You're fine to here.

  > Apply diff to old snapshot. Compare against new snapshot. Complain if there
  > is any discrepancy.
We don't do this.  As the snapshot process becomes more automated this
might make sense.

  > For that matter, I noticed the empty byte-code files through diff myself.
  > They should have been apparent, wouldn't they.
You missed an arg to patch.  Whatever one that says to delete files
made empty by the patch process.

jeff



More information about the Gcc mailing list