From owner-freebsd-ports@FreeBSD.ORG Tue Sep 6 02:55:00 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 62A71106564A; Tue, 6 Sep 2011 02:55:00 +0000 (UTC) (envelope-from wenheping@gmail.com) Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by mx1.freebsd.org (Postfix) with ESMTP id 02B078FC0C; Tue, 6 Sep 2011 02:54:59 +0000 (UTC) Received: by qwg2 with SMTP id 2so4023579qwg.17 for ; Mon, 05 Sep 2011 19:54:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=NEIYIEvcILXWSn8y3103WWQ8NXWhECfMAzmGVqxP/Q4=; b=Ik66yDejWyLFPtkslG5AIt4boOWf3UbBehsVhyVZE7GT4Cgb38EUZjFbVRQSWJIxIY YeyH73kJuCJllDC6yRKhrKpXpSci1e+DqpDsMMHDeeQQgZmvQo2KcaKMUgUoQ5ncqibf GY7N1l5Zhl21HosFLIoBovuvYNb/PTtb0W0/s= MIME-Version: 1.0 Received: by 10.224.201.2 with SMTP id ey2mr3061447qab.3.1315277699087; Mon, 05 Sep 2011 19:54:59 -0700 (PDT) Received: by 10.224.74.16 with HTTP; Mon, 5 Sep 2011 19:54:59 -0700 (PDT) In-Reply-To: <20110906015729.GB13195@lonesome.com> References: <4E64C077.8050403@yandex.ru> <4E656B6E.5080105@FreeBSD.org> <20110906015729.GB13195@lonesome.com> Date: Tue, 6 Sep 2011 10:54:59 +0800 Message-ID: From: wen heping To: Mark Linimon Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Ports Mailing List , neal@nelson.name, Doug Barton , Ruslan Mahmatkhanov Subject: Re: Maintainership of py-zopetesting and py-zopeevent X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Sep 2011 02:55:00 -0000 2011/9/6 Mark Linimon : > On Mon, Sep 05, 2011 at 05:38:06PM -0700, Doug Barton wrote: >> My understanding is that we don't do port names with . in them. Can >> someone who knows more than I confirm one way or the other? > > The porter's handbook is ambiguous: > > =C2=A0The first letter of the name part should be lowercase. (The rest of > =C2=A0the name may contain capital letters, so use your own discretion wh= en > =C2=A0you are converting a software name that has some capital letters in= it.) > =C2=A0There is a tradition of naming Perl 5 modules by prepending p5- and > =C2=A0converting the double-colon separator to a hyphen; for example, the > =C2=A0Data::Dumper module becomes p5-Data-Dumper. > > But, in "Here are some (real) examples on how to convert the name as > =C2=A0called by the software authors to a suitable package name:": > > v3.3beta021.src =C2=A0 =C2=A0 =C2=A0 =C2=A0 (empty) =C2=A0 =C2=A0 =C2=A0 = =C2=A0 tiff =C2=A0 =C2=A0(empty) =C2=A0 =C2=A0 =C2=A0 =C2=A0 3.3 =C2=A0 =C2= =A0 What the heck was that anyway? > > I'm not sure I see a compelling reason to change an existing name in > this case, anyways. Because we plan import new version Zope into portstree , it will create many new ports, so we only discuss this problem related to zope. Historically in FreeBSD portstree it had at least 3 kinds of naming of these zope-related ports, for example, now I shall create zope.browser ports,: 1) py-zope.browser 2) py-zopeBrowser 3) py-zope-browser which name is the best choice? I remember lwshu@ emailed the similar problem to portsmgr@ to ask for the answer but did not get a explicit one. I do not know which one is the best choice , but I think better we shall use the same naming type for all these zope-related ports. Because there were many zope-related ports in current portstree use the choice 1, so I think better rename others to the same naming type. wen > > mcl > >