Date: Mon, 5 Sep 2011 20:57:29 -0500 From: Mark Linimon <linimon@lonesome.com> To: Doug Barton <dougb@FreeBSD.org> Cc: FreeBSD Ports Mailing List <ports@freebsd.org>, neal@nelson.name, wen heping <wenheping@gmail.com>, Ruslan Mahmatkhanov <cvs-src@yandex.ru> Subject: Re: Maintainership of py-zopetesting and py-zopeevent Message-ID: <20110906015729.GB13195@lonesome.com> In-Reply-To: <4E656B6E.5080105@FreeBSD.org> References: <4E64C077.8050403@yandex.ru> <CACi7718digBBkknROiiMXWKHj9J1dx7jZ_VRGD3Q-Pi6fpLDtQ@mail.gmail.com> <4E656B6E.5080105@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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: The first letter of the name part should be lowercase. (The rest of the name may contain capital letters, so use your own discretion when you are converting a software name that has some capital letters in it.) There is a tradition of naming Perl 5 modules by prepending p5- and converting the double-colon separator to a hyphen; for example, the Data::Dumper module becomes p5-Data-Dumper. But, in "Here are some (real) examples on how to convert the name as called by the software authors to a suitable package name:": v3.3beta021.src (empty) tiff (empty) 3.3 What the heck was that anyway? I'm not sure I see a compelling reason to change an existing name in this case, anyways. mcl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110906015729.GB13195>