From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9217 invoked from network); 6 Jun 2001 16:37:53 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 6 Jun 2001 16:37:53 -0000 Received: (qmail 3998 invoked by alias); 6 Jun 2001 16:37:33 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14774 Received: (qmail 3986 invoked from network); 6 Jun 2001 16:37:32 -0000 Subject: Re: Module namespaces? RE: PATCH: zftp/tcp abstraction In-Reply-To: <003601c0eea6$7e5315d0$21c9ca95@mow.siemens.ru> from Andrej Borsenkow at "Jun 6, 2001 08:34:01 pm" To: Andrej Borsenkow Date: Wed, 6 Jun 2001 17:37:43 +0100 (BST) CC: zsh-workers@sunsite.dk X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: From: Zefram Andrej Borsenkow wrote: >What is the module nameing policy? It is somewhat silly to invent >hierarchical module namespace and put all modules under the same hood. My intention was that the first part of the hierarchical name identify the publisher of the module. For example, there could hypothetically be a module named "redhat/foo" published by Red Hat. The "zsh/" prefix is intended for all (and only) modules published by the Zsh Development Group. -zefram