Date: Wed, 18 May 2011 17:35:52 +0200 From: Baptiste Daroussin <bapt@freebsd.org> To: Joe Marcus Clarke <marcus@freebsd.org> Cc: Jason Helfman <jhelfman@e-e.com>, Doug Barton <dougb@freebsd.org>, doc-committers@freebsd.org, cvs-all@freebsd.org, cvs-doc@freebsd.org Subject: Re: cvs commit: doc/en_US.ISO8859-1/books/porters-handbook book.sgml Message-ID: <BANLkTinGehGSdK_4pAgpFmEHo4AL6BWnaA@mail.gmail.com> In-Reply-To: <4DD3E493.8010201@freebsd.org> References: <201105141806.p4EI6upK087278@repoman.freebsd.org> <4DCEEA98.4090300@FreeBSD.org> <800a75fbf37a5bf34858274adf2b5cb5.squirrel@mail.experts-exchange.com> <4DD3E493.8010201@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2011/5/18 Joe Marcus Clarke <marcus@freebsd.org>: > On 5/17/11 10:40 AM, Jason Helfman wrote: >> I put this patch in due to COMMENT being cut off at 60 characters. > > That makes sense, but given that we have other tools and sites that > provide port information, is it better to recommend the shorter COMMENT > that may not be sufficient to give a port intro, or should we opt for a > slightly longer string? =A0How will pkgng handle this? > pkgng does not have any limitation on comments, so it won't be a problem for that. regards, Bapt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTinGehGSdK_4pAgpFmEHo4AL6BWnaA>