From owner-freebsd-ports Tue Feb 26 15:54: 1 2002 Delivered-To: freebsd-ports@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id 1742437B423; Tue, 26 Feb 2002 15:53:46 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D422B66C32; Tue, 26 Feb 2002 15:53:45 -0800 (PST) Date: Tue, 26 Feb 2002 15:53:45 -0800 From: Kris Kennaway To: developers@FreeBSD.org, ports@FreeBSD.org Subject: Portmgr policy info (Re: (FWD) Re: Portmgr status (Re: Portmgr elections)]) Message-ID: <20020226155345.B76749@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="rS8CxjVDS/+yyDmU" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --rS8CxjVDS/+yyDmU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable ----- Forwarded message from Kris Kennaway ----- Delivered-To: kkenn@localhost.obsecurity.org Delivered-To: kris@freebsd.org Date: Tue, 26 Feb 2002 12:56:21 -0800 From: Kris Kennaway To: David O'Brien Cc: portmgr@freebsd.org, core@freebsd.org Subject: Re: (FWD) Re: Portmgr status (Re: Portmgr elections) User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020226123810.C87429@dragon.nuxi.com>; from obrien@freebsd.o= rg on Tue, Feb 26, 2002 at 12:38:10PM -0800 X-UIDL: 6297bfc086fabd7d0a79d27b82c970ea On Tue, Feb 26, 2002 at 12:38:10PM -0800, David O'Brien wrote: > I am submitting this as something I would like an offical responce to. > 1. What is portmgr's answer to the repo copy issue? We're discussing the issue based on committer input, and hope to have a new policy shortly. > 2. Other than we have the 4-exp ports run, what can you tell us about= how > often it is run, and who specifically we need to get a patch in > their hands to have it tested this way? It's run in series with the 4.x and 5.x package runs, if there are any patches in the 4-exp tree. Proposed bsd.port.mk patches should be send-pr'ed and assigned to portmgr so we have a record of them, and they are applied to the 4-exp tree by portmgr members, who all have write access to the 4-exp tree (without needing root). Once a patch is applied it will be built the next time 4-exp comes around in the cycle. If it completes the package build without causing any breakage (see the comparison 4-exp/4 logs on http://bento.freebsd.org) then it will be committed to the tree. > 3. What is the explicit mechanism for getting a new ports committer > approved? Submit the application to portmgr for voting. If approved by portmgr, we'll CC admin indicating as such, and the mentor and/or mentee submits their account information as usual. To head off what I expect you'll say next, we've already announced our intention to find a portmgr secretary to make sure we stop losing track of issues once they've been voted upon. Kris ----- End forwarded message ----- --rS8CxjVDS/+yyDmU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8fCAJWry0BWjoQKURAtNYAJ9FwcQziMXTrGzT2rRcLS4qyosLRwCfSTBN rUL4ui/6fgkqmuIoCnalhLs= =gF4D -----END PGP SIGNATURE----- --rS8CxjVDS/+yyDmU-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message