cvs commit: doc/en_US.ISO8859-1/books/porters-handbook book.sgml
jhelfman at e-e.com
Sat May 14 22:42:33 UTC 2011
On Sat, May 14, 2011 at 06:22:27PM -0400, Joe Marcus Clarke thus spake:
>On 5/14/11 5:47 PM, Doug Barton wrote:
>> On 05/14/2011 14:23, Joe Marcus Clarke wrote:
>>> On 5/14/11 4:48 PM, Doug Barton wrote:
>>>> Isn't the issue whether or not 70 characters will wrap in any of the
>>>> places that COMMENT is used?
>>> That's a concern, but the fact is most people base the length of COMMENT
>>> on the recommendation of portlint (which has been 70 characters
>>> forever). No one has complained about COMMENT wrapping at 70 characters
>>> that I have heard of. Do you know of any place where a COMMENT> 60
>>> characters wraps?
>> You're the one asserting that 70 characters is safe. :)
>I'm asserting that people have been limiting their COMMENTs to 70
>characters based on portlint's recommendations for some time. pkg_info
>[-I] will truncate COMMENTs at 59 characters, but even with that limit,
>the COMMENTs may wrap. The goal is to give porters enough space to
>display a meaningful COMMENT while not overflowing a standard 80 column
>terminal. When viewing the COMMENT in the Makefile strlen(COMMENT=) +
>70 < 80.
I updated the handbook sometime ago to the limit of 60, from 70. Is that incorrect? I
do agree, though, that portlint should warn on that.
>Joe Marcus Clarke
>FreeBSD GNOME Team :: gnome at FreeBSD.org
>FreeNode / #freebsd-gnome
>cvs-doc at freebsd.org mailing list
>To unsubscribe, send any mail to "cvs-doc-unsubscribe at freebsd.org"
E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5
More information about the cvs-all