From owner-freebsd-ports  Wed Jul  8 04:29:34 1998
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA08906
          for freebsd-ports-outgoing; Wed, 8 Jul 1998 04:29:34 -0700 (PDT)
          (envelope-from owner-freebsd-ports@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08789;
          Wed, 8 Jul 1998 04:29:03 -0700 (PDT)
          (envelope-from jkoshy@FreeBSD.org)
From: Joseph Koshy <jkoshy@FreeBSD.ORG>
Received: (from jkoshy@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id EAA02089;
	Wed, 8 Jul 1998 04:28:57 -0700 (PDT)
Date: Wed, 8 Jul 1998 04:28:57 -0700 (PDT)
Message-Id: <199807081128.EAA02089@freefall.freebsd.org>
To: ports@FreeBSD.ORG
Subject:  A peculiar port; advice requested ...
Cc: jkoshy@FreeBSD.ORG
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Hi,

I'm trying to make a port of Standard ML/NJ (an ML implementation from Bell
labs).  This is a somewhat unusual port, so I'd like to ask the list for
suggestions on how to tackle the porting process.  Names of ports which handle
similar issues will do fine!

Quirks:

1. While the official master site uses a ".tar.Z" suffix for most files,
   some of the mirrors use ".tar.gz" instead.  

   Any nice way of handling this in the ports framework (short of writing
   scripts for the entire fetch process that is)?

2. The install process involves a recompilation of (a) the runtime system
   and (b) the SML/NJ standard libraries.  The default installation 
   process expects to do this `in-place' in the final installation
   directory tree.

   I'm somehow not comfortable with a compilation under /usr/local as 
   part of `make'; however is it acceptable?  Does any other port do 
   anything similar?

3. Is creating a new hierarchy root say "${PREFIX}/sml-nj" ok?  The default
   installation expects "bin", "bin.${ARCH}", "lib"  etc. under
   this `ROOT'.  Changing the installation to confirm to a more
   conventional "/usr/local/*/" structure would make a FreeBSD SML/NJ
   installation different from the other unix installations.  Do
   we have a strict policy on directory hierarchies?

Thanks,
Koshy
<jkoshy@freebsd.org>

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message