From owner-freebsd-ports Wed Oct 16 21:22:59 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA01799 for ports-outgoing; Wed, 16 Oct 1996 21:22:59 -0700 (PDT) Received: from dfw-ix1.ix.netcom.com (dfw-ix1.ix.netcom.com [206.214.98.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA01794 for ; Wed, 16 Oct 1996 21:22:55 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca8-43.ix.netcom.com [207.93.141.171]) by dfw-ix1.ix.netcom.com (8.6.13/8.6.12) with ESMTP id VAA05060; Wed, 16 Oct 1996 21:22:21 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.6/8.6.9) id VAA03022; Wed, 16 Oct 1996 21:22:19 -0700 (PDT) Date: Wed, 16 Oct 1996 21:22:19 -0700 (PDT) Message-Id: <199610170422.VAA03022@silvia.HIP.Berkeley.EDU> To: james@nexis.net CC: freebsd-ports@freebsd.org In-reply-to: (message from James FitzGibbon on Wed, 16 Oct 1996 23:09:38 -0400 (EDT)) Subject: Re: Perl5 ports - how to name. From: asami@freebsd.org (Satoshi Asami) Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * So, the above module's PKGNAME would be perl5:Time::CTime. It looks ugly, * but with the possibilty of 100+ ports, they need to be sectioned off * somehow . Making a new directory for them is out, so this is the next * best thing. Well if you are really going to import 100+ ports, we should probably think about a separate directory. If for nothing else than to remove the "perl5" prefix from the subdirectory names. ;) That won't really change anything about the PKGNAME though, there are some places that all ports are listed together. How about "perl5-Time-CTime"? I have nothing against colons personally, but I'm not sure if the same can be said about all the utilities lying out there. Also I'm trying to standardize the PKGNAMEs, and connecting components with dashes is already sort of standard ("jp-mh-6.8.3", etc.). Satoshi