[packagers] Buildlog naming

[Dag Wieers]

Hi all,

Since a few days I have started using a different buildlog filename. It
used to be eg:

	unfs3-0.9.14-1.el4.rf.i386.log.gz

and it now is either:

	unfs3-0.9.14-1.el4.rf.i386.ok.log.gz
or
	unfs3-0.9.14-1.el4.rf.i386.ko.log.gz

The aim is to make it obvious to anyone without looking at the content of
the file whether it build or not. My buildsystem is now also a lot smarter
regarding knowing whether a build succeeded or not. It used to trust the
return code of rpmbuild, but that is not really trustworthy.

>From now on dar-build does the right thing and inspects the logfile to see
if an RPM was actually produced. And that is reflected in the buildlog
filename from now.

I hope that we can have a similar convention with the new tools I am
preparing (DAR for the masses) so that buildlog files contain _all_
information concerning a build and can be compared between builds.

Being able to compare buildlogs is something that can help find
individual build problems. Within rpmrepo I hope we can come to a
consensus wrt. the content and the filename of the buildlog.

-- 
--   dag wieers,  dag at wieers.com,  http://dag.wieers.com/   --
[Any errors in spelling, tact or fact are transmission errors]