From owner-freebsd-ports@FreeBSD.ORG Fri Mar 26 08:25:21 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0797A16A4CE for ; Fri, 26 Mar 2004 08:25:21 -0800 (PST) Received: from sirius.firepipe.net (sirius.firepipe.net [69.13.116.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 927D443D39 for ; Fri, 26 Mar 2004 08:25:20 -0800 (PST) (envelope-from will@csociety.org) Received: by sirius.firepipe.net (Postfix, from userid 1000) id 9DFA8ED2; Fri, 26 Mar 2004 11:25:15 -0500 (EST) Date: Fri, 26 Mar 2004 11:25:15 -0500 From: Will Andrews To: Sergey Matveychuk Message-ID: <20040326162515.GB57192@sirius.firepipe.net> Mail-Followup-To: Sergey Matveychuk , Robin Schoonover , naddy@mips.inka.de, freebsd-ports@freebsd.org References: <4062FF7A.2040509@ciam.ru> <20040326011325.4AA3B43D5D@mx1.FreeBSD.org> <40642549.6050202@ciam.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dc+cDN39EJAMEtIO" Content-Disposition: inline In-Reply-To: <40642549.6050202@ciam.ru> User-Agent: Mutt/1.4.1i cc: freebsd-ports@freebsd.org cc: naddy@mips.inka.de cc: Robin Schoonover Subject: Re: Sign your name in pkg-descr is useless or useful? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Mar 2004 16:25:21 -0000 --dc+cDN39EJAMEtIO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 26, 2004 at 03:42:49PM +0300, Sergey Matveychuk wrote: > And desctribe target should be fixed too for backward compatible. > But it's quite easy. I'm not sure for bento scripts and may be something= =20 > more? >=20 > Anyway a patch can be ready for a few minutes. But what portmgr thinks? I think centralizing these formatting outputs is a good idea. We can also set rules for how "MAINTAINER" should be formatted. How about this: MAINTAINER=3D email@address Name1 Name2 Name3 ... =2E.. this will still allow programs that interpret MAINTAINER directly by taking the second field (whitespace delimiter) to work correctly, and makes writing said function simple. Regards, --=20 wca --dc+cDN39EJAMEtIO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAZFlrF47idPgWcsURAlESAJ0UP/52WVkvc+hv5brfHEX7LG/w+wCbBpiS k4dxatLLQMfl5kA1xFiWju8= =+3Y4 -----END PGP SIGNATURE----- --dc+cDN39EJAMEtIO--