From owner-freebsd-ports Sat Oct 14 7:11:27 2000 Delivered-To: freebsd-ports@freebsd.org Received: from toyland.drapple.com (toyland.drapple.com [204.200.26.114]) by hub.freebsd.org (Postfix) with ESMTP id 21FD037B66C; Sat, 14 Oct 2000 07:11:26 -0700 (PDT) Received: from freebsd.org (adsl-151-196-243-89.bellatlantic.net [151.196.243.89]) by toyland.drapple.com (8.9.3/8.9.3) with ESMTP id HAA06291; Sat, 14 Oct 2000 07:11:24 -0700 (PDT) (envelope-from patrick@freebsd.org) Message-ID: <39E8693C.18DB312E@freebsd.org> Date: Sat, 14 Oct 2000 10:10:04 -0400 From: Patrick Gardella Organization: FreeBSD X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: asami@freebsd.org, ports@freebsd.org Subject: Large Port Builds References: <39E73443.848834FE@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Do we have, or have we considered adding "notices" to ports that take a large amount of time and/or disk space to build to the Makefile? For instance, the new java/jdk12-beta port can take up to 250MB of disk space to build. I want to see huge ports like this availible, but at the same time, I remember a time when I was running FreeBSD on an old 486, and a port like this would have taken days to build, not to mention, half my hard drive. I'd like to suggest that we add two items to either pkg-descr or the Makefile: BUILD_SIZE= rough size of space needed to complete build and install (i.e. maximum size) INSTALLED_SIZE= rough size of final space need to install (i.e. package size) Then modify the make routines to determine from the BUILD_DEPENDS and RUN_DEPENDS how much space you will need to complete this build based on what you still need to install. Does this make sense? Should we (I) do it? -- Patrick ---------- Patrick Gardella patrick@freebsd.org The Power to Serve shall not be infringed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message