Hi,
On Thu, 11 Apr 2002, Keith Owens wrote:
> There can be multiple destination files, e.g. running yacc produces a
> .c and a .h file.
The checksum only needs to be stored in one of them.
> The generated file is not necessarily .[ch], wrapping the md5sum in
> /* */ may break some generated files. AFAIK all currently generated
> files are .[ch] but I do not want to restrict future builds.
The wrapping could be changed with an argument and if everything fails,
the checksum can still be put into a separate file.
> The output can change without the inputs changing. For example, the
> distributor might find a bug in the tool that generates the file,
> install a new version of the tool and regenerate. The inputs have not
> changed but the output has. To detect this, the md5sum is across all
> files, including the outputs, which makes it impossible to store the
> sum in one of the output files.
What exactly are you detecting? Simply regenerate the files and distribute
the changes, the checksum won't change, but I don't understand how that
should matter.
What other problem are you trying to solve? My simple script solves the
problem of unreliable time stamps, when applying patches. Unless the user
changes the inputs, the output files won't be regenerated.
bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Apr 15 2002 - 22:00:18 EST