From owner-freebsd-libh Sat Oct 20 20:21:55 2001 Delivered-To: freebsd-libh@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 885) id 22F3937B405; Sat, 20 Oct 2001 20:21:53 -0700 (PDT) Date: Sat, 20 Oct 2001 20:21:53 -0700 From: Eric Melville To: binup@FreeBSD.org Cc: libh@FreeBSD.org Subject: current project steps Message-ID: <20011020202153.A76835@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-libh@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The way I see it, the big picture steps for binup are: 1. Extend package framework with middle layer API and system packages 2. Work concept of system packages into the FreeBSD tree 3. Create library with basic portupgrade functionality and network protocol 4. Write applications that use this library to update the system Use of binup and the source tree should not be mutually exclusive. It should be possible to upgrade a system from source, then a month later, upgrade it with binup, and then return using the source tree without hassle. This is not trivial, but assumedly could be accomplished by using the mk makefiles to register system components in the package database as it installs them. Additionally, after the client library is completed, I would like to make usage of a binup server a valid means of installation for libh. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-libh" in the body of the message