"make readmes" seems to be broken (again)

Jason Helfman jhelfman at e-e.com
Thu Jan 12 21:29:54 UTC 2012

Hash: SHA256

On Tue, Dec 13, 2011 at 04:48:38PM -0800, Jason Helfman thus spake:
>On Sat, Dec 03, 2011 at 05:31:49PM -0600, Conrad J. Sabatier thus spake:
>>I've just noticed recently that "make readmes" in ports is acting up
>>again (I reported a similar problem several months ago, which did get
>>fixed at the time).
>>Instead of generating a README.html at the top level, category level,
>>and individual packages level, only the top-level and category-level
>>files are being generated.  No README.html files are being generated at
>>the individual package level.
>>I saw (and reported) this same behavior about four months ago, and it
>>did, as I said, get fixed back then.  No idea why it's suddenly broken
>>again now.
>>Can anyone confirm that it's not just a local problem for me, that it
>>is indeed broken for everyone?
>Thanks for the report. I have run a job through the portstree to build all
>readme's and found several ports that are affected by this issue and
>submitted problem reports for them.
>All ports that broke redefined ${ECHO_MSG} which had issues with a target in
>bsd.port.mk. The affected target was: pretty-print-www-site

I have committed all of these fixes, so there shouldn't be any more breakage
in the portstree insofar as 'make readme' functionality. We are working on a
larger programmatic fix so this can be handled more efficiently.

Please continue to send reports in if any others surface.

Thanks, again!

- -jgh

- -- 
Jason Helfman
System Administrator
E4AD 7CF1 1396 27F6 79DD  4342 5E92 AD66 8C8C FBA5
Version: GnuPG v2.0.18 (FreeBSD)


More information about the freebsd-ports mailing list