From owner-freebsd-ports@FreeBSD.ORG  Fri Feb  6 06:00:36 2004
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 00DFE16A4CF
	for <freebsd-ports@freebsd.org>; Fri,  6 Feb 2004 06:00:36 -0800 (PST)
Received: from nhugin.diku.dk (nhugin.diku.dk [130.225.96.140])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 916DB43D39
	for <freebsd-ports@freebsd.org>; Fri,  6 Feb 2004 06:00:34 -0800 (PST)
	(envelope-from debois@diku.dk)
Received: by nhugin.diku.dk (Postfix, from userid 754)
	id C197E6E1290; Fri,  6 Feb 2004 15:00:23 +0100 (CET)
Received: from tyr.diku.dk (tyr.diku.dk [130.225.96.226])
	by nhugin.diku.dk (Postfix) with QMQP id 832A56E1238
	for <freebsd-ports@freebsd.org>; Fri,  6 Feb 2004 15:00:23 +0100 (CET)
Date: Fri, 6 Feb 2004 15:00:33 +0100
From: =?iso-8859-1?Q?S=F8ren?= Debois <debois@diku.dk>
To: freebsd-ports@freebsd.org
Message-ID: <20040206140033.GA10686@diku.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	nhugin.diku.dk
X-Spam-Level: 
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.60
Subject: Renaming port moscow_ml
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2004 14:00:36 -0000

Hi there, 

I've been working on the lang/moscow_ml port. I'd like to submit the
changes as a new port 'mosml-2.01', since this is the name generally
used for the Moscow ML system.

Is this a no-no? Is there some procedure for doing this?

In case anybody cares, here's the list of updates:

        - New upstream version
        - Flag as RESTRICTED
        - Avoid installing everything under ${PREFIX}/mosml
        - Installs more examples 
        - Fix broken installation of dynamically loaded modules
        - Add installation of Regex dyn. loaded interface.
        - Add installation of readmes and licensing stuff
        - Respect NOPORTDOCS

-- 
	--- Debois