Date: Sat, 14 May 2011 23:33:38 -0400 From: Joe Marcus Clarke <marcus@freebsd.org> To: Doug Barton <dougb@freebsd.org> Cc: doc-committers@freebsd.org, cvs-doc@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: doc/en_US.ISO8859-1/books/porters-handbook book.sgml Message-ID: <4DCF4992.3010008@freebsd.org> In-Reply-To: <4DCF0210.2030303@FreeBSD.org> References: <201105141806.p4EI6upK087278@repoman.freebsd.org> <4DCEEA98.4090300@FreeBSD.org> <4DCEF2E8.8060106@freebsd.org> <4DCEF864.50105@FreeBSD.org> <4DCF00A3.9090100@freebsd.org> <4DCF0210.2030303@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/14/11 6:28 PM, Doug Barton wrote: > On 05/14/2011 15:22, Joe Marcus Clarke wrote: >> pkg_info >> [-I] will truncate COMMENTs at 59 characters > > Then shouldn't that be the limit? "It's been done wrong for a long time" > isn't a good reason to keep doing it wrong, IMO. I agree, but I'm not sure pkg_info is the right way of doing things. Even with pkg_info's 59 character limit, some lines do wrap. I'd much rather authors be given the extra 10 characters to produce a more meaningful COMMENT (if they need it) than cut them short for the purposes of the one output of one tool; especially if people typically look at other tools/sites (which do not truncate) to learn about ports they want to install. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DCF4992.3010008>