From owner-freebsd-ports  Sun Nov  9 09:51:36 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id JAA24830
          for ports-outgoing; Sun, 9 Nov 1997 09:51:36 -0800 (PST)
          (envelope-from owner-freebsd-ports)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA24822
          for <freebsd-ports@FreeBSD.ORG>; Sun, 9 Nov 1997 09:51:33 -0800 (PST)
          (envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id JAA09931; Sun, 9 Nov 1997 09:51:01 -0800 (PST)
To: James Raynard <fports@jraynard.demon.co.uk>
cc: freebsd-ports@FreeBSD.ORG
Subject: Re: Porting without tarballs 
In-reply-to: Your message of "Sun, 09 Nov 1997 12:24:20 GMT."
             <19971109122420.39804@jraynard.demon.co.uk> 
Date: Sun, 09 Nov 1997 09:51:01 -0800
Message-ID: <9927.879097861@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-ports@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I have two more ports which are ready to be committed, once I can get
> over the last hurdle.  The problem is there is no tarball for either of
> the ports; the source is on an FTP server that doesn't support on-the-fly
> tarring (and in any case I have a nasty suspicion they may soon delete it).
> 
> The best solution seems to make my own tarball and put it on
> ftp.freebsd.org.  Is this correct, and if so how do I go about it?

Actually, historically we've been putting such things up at
ftp://hub.freebsd.org/pub/FreeBSD/LOCAL_PORTS which, as a ports
committer, you should be able to write to directly.

					Jordan