From owner-freebsd-ports Fri Mar 30 18: 0: 7 2001 Delivered-To: freebsd-ports@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1E42737B71B for ; Fri, 30 Mar 2001 18:00:04 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f2V204a25730; Fri, 30 Mar 2001 18:00:04 -0800 (PST) (envelope-from gnats) Date: Fri, 30 Mar 2001 18:00:04 -0800 (PST) Message-Id: <200103310200.f2V204a25730@freefall.freebsd.org> To: freebsd-ports@FreeBSD.org Cc: From: Will Andrews Subject: Re: ports/26155: New port: security/py-m2crypto Reply-To: Will Andrews Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR ports/26155; it has been noted by GNATS. From: Will Andrews To: will@FreeBSD.org Cc: peterh@sapros.com, FreeBSD GNATS DB Subject: Re: ports/26155: New port: security/py-m2crypto Date: Fri, 30 Mar 2001 20:50:22 -0500 On Fri, Mar 30, 2001 at 05:51:56PM -0800, will@FreeBSD.org wrote: > Committed, thanks. I made numerous cleanups on your Makefile, and > in general I think the port is much cleaner now. In particular, I > took advantage of [pre,post]-build, PLIST_SUB, and ${TMPPLIST}. Also, I put this port in the security category, because it's a wrapper for OpenSSL, which is in the same category. --=20 wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message