From owner-freebsd-ports Sat Apr 22 17:47:33 2000 Delivered-To: freebsd-ports@freebsd.org Received: from kenny.blue-box.net (kenny.blue-box.net [199.2.205.167]) by hub.freebsd.org (Postfix) with ESMTP id 560B337B5A8 for ; Sat, 22 Apr 2000 17:47:31 -0700 (PDT) (envelope-from vince@bendnet.com) Received: from kenny.blue-box.net (kenny.blue-box.net [199.2.205.167]) by kenny.blue-box.net (8.10.1/8.10.1/BBMX) with ESMTP id e3N0mBR70940; Sat, 22 Apr 2000 17:48:11 -0700 (PDT) Date: Sat, 22 Apr 2000 17:48:11 -0700 (PDT) From: Vince Valenti To: Will Andrews Cc: freebsd-ports@FreeBSD.ORG Subject: Re: syslog-ng In-Reply-To: <20000422202906.I6549@argon.blackdawn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 22 Apr 2000, Will Andrews wrote: > http://www.FreeBSD.org/handbook/porting.html for future reference. > > Make sure you've checked the port with ``portlint -a -c'', then submit it > as a shar. I prefer this method for shar-generation: > > [will@shadow /usr/ports/devel/popt]% cd .. > [will@shadow /usr/ports/devel]% shar `find popt` > popt.shar > > This way, if you choose the wrong category for a port, I can easily change > that by cd'ing to the right one and unsharing the new port. Thanks Will... I have one more question. On a port like syslog-ng, which is a replacement for the standard syslogger, how should it get started? Should I tell the user to edit their rc.conf, or create a script in rc.d? Thanks, -- Vince Valenti Network Services BendNet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message