Re: install-guide rpm-info.xml,1.2,1.3

[Tommy Reynolds]

Uttered "Paul W. Frields" <stickster(a)gmail.com&gt;, spake thus:

>  re: Commit below --
>  
>  On Tue, 2006-01-17 at 18:04 -0500, Tommy Reynolds wrote:
>  > Log Message:
>  > Dates must be in ctime(3) format, not ISO format.
>  > TODO: We need an XSL magic to translate the dates if they have dashes. 
I added the "fdpsh" command "iso2date YYYY-MM-DD" or "iso2date
today"
to make this easier.
 
>  The "make clog" target takes care of this automatically.  I
> would
>  recommend folks using that target whenever possible since it minimizes
>  hassle.  If you edit manually, well, just respect the normal rules for
>  such things.  If you break the revision's @date attribute, the rpmbuild
>  process will tell you what you did wrong (i.e. %changelog date is not in
>  proper format). 
All dates in the "rpm-info.xml" file should be in the ctime(3)
format, instead of some as ISO and others not.  We just don't really
care about the revision date on the doc.  Yet.
 
>  Since no one will be creating rpm-info.xml files that have any RPM
>  revisions yet, there shouldn't be any cruft to worry about. 
Well, I'm testing the RPM build structure on a second document ;-)
I'm not really sure how this "rpm-info.xml" was produced, though.

As you say, no need to worry.  In fact, I only worry about those
things which I control: therefore, I never worry about anything.

Cheers