From owner-freebsd-stable Sat Oct 23 23:32: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (Postfix) with ESMTP id 26772150E1; Sat, 23 Oct 1999 23:31:44 -0700 (PDT) (envelope-from asami@sunrise.cs.berkeley.edu) Received: from bubble.didi.com (sji-ca3-59.ix.netcom.com [209.109.233.59]) by vader.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id XAA07612; Sat, 23 Oct 1999 23:31:40 -0700 (PDT) (envelope-from asami@sunrise.cs.berkeley.edu) Received: (from asami@localhost) by bubble.didi.com (8.9.3/8.8.8) id WAA40169; Sat, 23 Oct 1999 22:01:28 -0700 (PDT) (envelope-from asami) To: Kris Kennaway Cc: "Jeffrey J. Libman" , freebsd-stable@FreeBSD.ORG Subject: Re: building pgp5 from ports fails References: From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 23 Oct 1999 22:01:24 -0700 In-Reply-To: Kris Kennaway's message of "Sun, 17 Oct 1999 15:52:07 -0700 (PDT)" Message-ID: Lines: 16 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Kris Kennaway * Having said that, is there any way you could get bento building restricted * ports, but not publishing the packages? It's quite useful for the kind of * thing I tried to apply it to (i.e. figuring out whether the port itself is * broken, or if it's just the local setup). That's a good idea. Since the packages are copied over to ftp.FreeBSD.org only once per week, there shouldn't be any problem building RESTRICTED ports during other times. Actually, since it now creates a restricted.sh file that can be used to remove restricted packages and distfiles, maybe I can always build everything and run the script before copying the files over.... -PW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message