Whenever I install a new release on my LabRat for testing I also load
the ports tree and build the packages I cannot get from ftp servers.
e.g. the not for FTP or ones I need a different flavor in.
So when the new CDs arrived I loaded the tree and then went to
/usr/ports and did a make readmes. Pretty soon it bombed with an error.
My usual Q&D fix is to comment out the relevant line in the category
Makefile. In previous years there was either no bug or maybe one. 4.2
has quite a few so I did:
make -ks readmes >realog 2>&1
and found "25 Error code 1" lines.
Most are unexpected "(", a few missing closing quote.
So far I've found that, for all that I've hunted, bugs in are caused by
comments containing a posessive single quote or something in
parentheses.
I've fixed them by enclosing the entire comment in double quotes.
Is this the best way? If so how about making it a "rule" for ports
Makefile contents?
Alternatively I volunteer to do readmes QC on the ports.tar.gz any time
(if I'm here, which is 98% of the time except for a couple of weeks
around Xmas) as soon as I can after Marc Espie points me at a candidate
tarball I can download. If he accepts I'll provide him with an
exclusive email address to use.
I can do diffs (better for the CVS?) or return corrected files or the
complete tarball with no errors showing.
Howzat?
Rod/
>From the land "down under": Australia.
Do we look <umop apisdn> from up over?
