From owner-freebsd-ports@FreeBSD.ORG Thu Jun 13 14:25:15 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E4D6C9BA for ; Thu, 13 Jun 2013 14:25:15 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from slim.berklix.org (slim.berklix.org [94.185.90.68]) by mx1.freebsd.org (Postfix) with ESMTP id 5BA961F81 for ; Thu, 13 Jun 2013 14:25:15 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBFE18.dip0.t-ipconnect.de [93.203.254.24]) (authenticated bits=128) by slim.berklix.org (8.14.5/8.14.5) with ESMTP id r5DDbXg3077298; Thu, 13 Jun 2013 15:37:34 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r5DDbP31036504; Thu, 13 Jun 2013 15:37:25 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r5DDbFYx089572; Thu, 13 Jun 2013 15:37:20 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201306131337.r5DDbFYx089572@fire.js.berklix.net> To: =?ISO-8859-2?Q?Jo=BEe_Zobec?= Subject: Re: Suggesting a new experimental fork for ports tree From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Wed, 12 Jun 2013 20:04:30 +0200." Date: Thu, 13 Jun 2013 15:37:15 +0200 Sender: jhs@berklix.com Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jun 2013 14:25:16 -0000 Hi, Reference: > From: =?ISO-8859-2?Q?Jo=BEe_Zobec?= > Date: Wed, 12 Jun 2013 20:04:30 +0200 > Apart from the maintainer of the port, there would also be "sub" > maintainerswhich would be those people who helped patch the port into the > good shape: > > # make -C /usr/ports/section/someport maintainer > > would return the maintainer (1st address) and additional addresses to turn > for questions. When the port would be committed to the "good" ports tree, > sub-maintainers would be left out. Maybe it'd help to break jozze.zepl's suggestions in to 2 parts ? - Working & non working ports tree (No comment from me on that) - Multiple maintainers I believe MAINTAINER= value is currently a unitary mail address, which is [usually] an individual or a freebsd mail list. I recall before we've discussed adding names of alternates/ extras, (perhaps comma seperated), & that some who maintain .mk macros & shell scripts pointed out some difficulties if changed. Even within the current unchanged syntax, handfulls of maintainers might already co-operate on a per port basis, with eg MAINTAINER=port_xyz_maintainers@their-domain.com their-domain.com /etc/mail/aliases: port_xyz_maintainers: port_xyz_maint0, port_xyz_maint1 port_xyz_maint0: jack@upthehill.com port_xyz_maint1: jill@downthehill.com Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative.