From owner-freebsd-ports Wed Sep 20 19:43:44 2000 Delivered-To: freebsd-ports@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 704E837B423 for ; Wed, 20 Sep 2000 19:43:42 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8L2hS620193 for ; Wed, 20 Sep 2000 19:43:28 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: ports@freebsd.org Subject: How to build packages on the fly... Date: Wed, 20 Sep 2000 19:43:28 -0700 Message-ID: <20189.969504208@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What I'm about to describe is something I'd like, not something which currently exists, and I'm just collecting some feedback on it before actualling diving into the implementation details. In a nutshell, what I'd like to be able to do is build a fresh version of package X and all the packages it has RUN_DEPENDS on easily so that I can pack those up and drop them into a packages tree somewhere. This is particularly useful for the big and complex packages, like KDE or GNOME. To be more specific, I'd like to be able to do: mkdir /usr/ports/packages cd /usr/ports/x11/kde2 make all install package .. and wind up with, in /usr/ports/packages/All, a complete set of packages required to support KDE version 2. What will happen now is something less desirable, which is essentially a make and install of the KDE master port and all the things it depends on, but only *one* package, that being for the KDE master port. Then I basically have to grep through all the output of the builds to find out which other ports were built so that I can individually package each one. Not quite the auto-recursion effect I was looking for. :( - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message