From owner-freebsd-ports  Thu Jan  1 16:27:57 1998
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id QAA22310
          for ports-outgoing; Thu, 1 Jan 1998 16:27:57 -0800 (PST)
          (envelope-from owner-freebsd-ports)
Received: from bubble.didi.com (sjx-ca124-61.ix.netcom.com [207.223.162.189])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA22297
          for <ports@freebsd.org>; Thu, 1 Jan 1998 16:27:53 -0800 (PST)
          (envelope-from asami@sunrise.cs.berkeley.edu)
Received: (from asami@localhost)
	by bubble.didi.com (8.8.7/8.8.7) id PAA16553;
	Thu, 1 Jan 1998 15:59:05 -0800 (PST)
	(envelope-from asami)
Date: Thu, 1 Jan 1998 15:59:05 -0800 (PST)
Message-Id: <199801012359.PAA16553@bubble.didi.com>
To: imdave@mcs.net
CC: hoek@hwcn.org, imdave@mcs.net, ports@freebsd.org
In-reply-to: <199801012113.PAA29660@base486.home.org> (message from Dave Bodenstab on Thu, 1 Jan 1998 15:13:51 -0600 (CST))
Subject: Re: ports/5393: DOOMSRC port :  package
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * Hi,

Hi.

 * I got some feedback from someone who (I guess) grabbed it from the
 * incoming directory, and he had a build problem with the X11 includes.
 * I've forgotten, but I think that I automatically do a symlink of
 * /usr/include/X11 --> /usr/X11R6/include on my machine, so I didn't
 * catch this problem.  I fixed this.

I see.  By the way, I'm recommending people working on ports to not
create that link.  (We've been bitten by this so many times....)

 * (I know -- I forgot it's 1998)  Do I use send-pr to mention this update?
 * Do I email someone?  Will I get some sort of feedback if the port is
 * ``accepted''?  If there is more feedback, and I need to update it in

If you have a committer working closely to you, just mailing that
person is fine.  If there is no such person (yet), send mail to
freebsd-gnats-submit@freebsd.org with the subject line same as this
message.  When it's committed, you'll at least see a mail saying the
PR is closed (maybe more, depending on the committer).

 * the future, how do I best do that?  Id's version is 1.10, so my first
 * take is that this should be the version number for the package -- is this
 * reasonable even tho the port is updated over time?

Yes.  Don't worry too much about micro-updates.  We're not in position
to manage updates with that kind of granurality.

Satoshi