From owner-freebsd-ports Sat May 17 04:43:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA21211 for ports-outgoing; Sat, 17 May 1997 04:43:04 -0700 (PDT) Received: from X2296 (ppp6467.on.sympatico.ca [206.172.208.59]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA21201; Sat, 17 May 1997 04:42:53 -0700 (PDT) Received: from localhost (tim@localhost) by X2296 (8.7.6/8.7.3) with SMTP id HAA00770; Sat, 17 May 1997 07:42:27 -0400 (EDT) Date: Sat, 17 May 1997 07:42:26 -0400 (EDT) From: Tim Vanderhoek Reply-To: ac199@hwcn.org To: Masafumi NAKANE cc: mcj@acquiesce.org, max@hub.freebsd.org, freebsd-ports@hub.freebsd.org Subject: Re: ports/3146 In-Reply-To: <199705161201.FAA24340@hub.freebsd.org> Message-ID: X-OS: FreeBSD 2.2 X-Mailer: Pine MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 16 May 1997, Masafumi NAKANE wrote: > Synopsis: new port fix (slrn) > > We already have slnr in our ports collection. > The only significant difference that the submitted port has is the contents of > files/porting.notes. > If slnr port in ports-current doesn't have any problem (well, it > shouldn't as the submitted one wasn't any different from it, though), Watch out! slrn := Simple Local Read News, slnr := Simple Local Newsreader. Slnr's claim to fame is that it can read and create SOUP packets. Slrn connects directly with newservers... -- tIM...HOEk Whoever told you I had a .signature was lying.