From owner-freebsd-binup Tue Oct 16 11: 0:58 2001 Delivered-To: freebsd-binup@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 885) id C424337B40B; Tue, 16 Oct 2001 11:00:56 -0700 (PDT) Date: Tue, 16 Oct 2001 11:00:56 -0700 From: Eric Melville To: Josef Karthauser Cc: Murray Stokely , binup@FreeBSD.org Subject: Re: design issues Message-ID: <20011016110056.E4211@FreeBSD.org> References: <20011014170515.B39749@FreeBSD.org> <20011014180507.D2654@windriver.com> <20011015020834.Y31066@tao.org.uk> <20011014181709.E2654@windriver.com> <20011015023057.A31066@tao.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011015023057.A31066@tao.org.uk>; from joe@tao.org.uk on Mon, Oct 15, 2001 at 02:30:57AM +0100 Sender: owner-freebsd-binup@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > * Use an SQL database to record info on installed packages instead of > using /var/db/pkg entries. > > * Plug new groups of ports in via a plug in module, like the bsdpan > (CPAN) for installed perl modules. Package tools shouldn't be using > /usr/ports/INDEX natively. They should be going through the API so > that other modules can advertise what they're able to install also. > There are loads of things that would benefit from this. Ruby, Latex, > CPAN, etc. > > All of this whilst still using the package tools that we know and love. An SQL database is a pretty steep dependancy for something as simple as this. What limitations do we have with a simple filesystem-based means of storage? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-binup" in the body of the message