From owner-freebsd-ports@FreeBSD.ORG Tue May 4 09:04:15 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D11A16A4CE for ; Tue, 4 May 2004 09:04:15 -0700 (PDT) Received: from ctb-mesg2.saix.net (ctb-mesg2.saix.net [196.25.240.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86EFF43D54 for ; Tue, 4 May 2004 09:04:12 -0700 (PDT) (envelope-from reg@lantic.net) Received: from local (wpaw-ip-nas-1-p59.telkom-ipnet.co.za [155.239.120.59]) by ctb-mesg2.saix.net (Postfix) with ESMTP id 92C5D170F; Tue, 4 May 2004 18:04:07 +0200 (SAST) Received: from local (shale.local [192.168.0.1]) by local (8.12.11/8.12.11) with ESMTP id i44G46Ix010380; Tue, 4 May 2004 18:04:06 +0200 (SAT) (envelope-from reg@local) Received: (from reg@localhost) by local (8.12.11/8.12.11/Submit) id i44G45BB010379; Tue, 4 May 2004 18:04:05 +0200 (SAT) (envelope-from reg) Date: Tue, 4 May 2004 18:04:05 +0200 From: Jeremy Lea To: Erich Dollansky Message-ID: <20040504160405.GA10349@shale.local> Mail-Followup-To: Jeremy Lea , Erich Dollansky , freebsd-ports@FreeBSD.ORG, fpkg-devel@lists.sourceforge.net References: <20040504091043.GA1051@shale.local> <4097B31D.9080205@pacific.net.sg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4097B31D.9080205@pacific.net.sg> User-Agent: Mutt/1.4.2.1i cc: freebsd-ports@FreeBSD.ORG cc: fpkg-devel@lists.sourceforge.net Subject: Re: FreePKG: An alternative to the pkg_* tools X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 May 2004 16:04:15 -0000 Hi, On Tue, May 04, 2004 at 11:13:33PM +0800, Erich Dollansky wrote: > >I have no intention of initiating any attempt to get these tools > >imported into FreeBSD. I've decided on a very different approach to the > >Ports/Packages collection to the way that things appear to be going. > >However, these tools are functional, and some people might find them > >useful. Additional developers/testers would be most welcome. > > So, how can a normal FreeBSD user make use of the tools? Yes, I suppose that would be useful information. :-) The following steps are needed. Since this is alpha quality at the moment, I would not use this on anything which you have to have... 1. Download and build a CVS version of the tools from: cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/fpkg login [Enter blank password] cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/fpkg co freepkg cd freepkg make && make install These tools currently install into /root/bin. I should change that to /usr/sbin or /usr/local/sbin. The tools are named fpkg* to not conflict with the FreeBSD versions. Change Makefile.inc to change the install path. 2. Download and patch bsd.port.mk cd /tmp fetch http://fpkg.sourceforge.net/bsd.port.mk-fpkg.patch cd /usr/ports/Mk/ patch -I < /tmp/bsd.port.mk-fpkg.patch Change the path to the tools (search for PKG_CMD) if you changed it above. 3. The bad news: Rebuild all your ports, so that the new tools are used... Regards, -Jeremy -- FreeBSD - Because the best things in life are free... http://www.freebsd.org/