From owner-freebsd-ports Sun Aug 23 23:32:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01150 for freebsd-ports-outgoing; Sun, 23 Aug 1998 23:32:12 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01046; Sun, 23 Aug 1998 23:31:25 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:qHIFzUwX+AUJ6V0mhARORXM/RJuiMi59@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id IAA24415; Mon, 24 Aug 1998 08:29:49 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199808240629.IAA24415@gratis.grondar.za> To: asami@FreeBSD.ORG (Satoshi Asami) cc: sfarrell@healthquiz.com, ports@FreeBSD.ORG Subject: Re: [comp.infosystems.www.browsers.ms-windows,comp.infosystems.www.browsers.misc,comp.infosystems.www.browsers.x,de.comm.infosystems.www.browsers,fj.net.infosystems.www.browsers] ANNOUNCE: 128-bit crypto: Fortify for Netscape v1.2.6 released Date: Mon, 24 Aug 1998 08:29:39 +0200 From: Mark Murray Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > * I think this means that fortify for the current port of 4.06 is > * broken... > > This seems to happen at every upgrade. How about we make > netscape4-{c*,n*}-fortify ports so they can be tracked separately? > Is that ok, Andrey? (And who wants to be the maintainer of the > *-fortify ports?) I am doing the fortify bits, and I am not too keen on that, although I'll do it if you insist. I'll be fixing the netscapes today. :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message