From owner-freebsd-ports@FreeBSD.ORG Sat Nov 10 07:52:08 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B8FB4D4D for ; Sat, 10 Nov 2012 07:52:08 +0000 (UTC) (envelope-from zaphod@berentweb.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 7DDBE8FC12 for ; Sat, 10 Nov 2012 07:52:08 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TX5rM-0001c1-24 for freebsd-ports@freebsd.org; Fri, 09 Nov 2012 23:52:08 -0800 Date: Fri, 9 Nov 2012 23:52:08 -0800 (PST) From: Beeblebrox To: freebsd-ports@freebsd.org Message-ID: <1352533928056-5759760.post@n5.nabble.com> In-Reply-To: <509D2619.9020105@shatow.net> References: <1352454789865-5759489.post@n5.nabble.com> <509CF2B0.5050008@egr.msu.edu> <1352464341903-5759519.post@n5.nabble.com> <509D2619.9020105@shatow.net> Subject: Re: pkgng woes MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 07:52:09 -0000 Bryan Drewery wrote > 1. This should not happen if you have the latest portmaster port and use > the PKGNGPATCH option. > 2. It is not required that you use binary packages with pkgng. You can > continue using ports with portmaster/portupgrade just fine. > 3. Portmaster *is* fully ready for pkgng, and does utilize the pkgng tools > to read from its database. Q1+Q3. That's not the point: For ports I have compiled + installed AFTER switching to pkgng and AFTER enabling PKGNGPATCH in portmaster, the pkgdb records are populated correctly. The problem is with the ports already installed on the system BEFORE the switch. Most of the records for those ports are corrupt and THERE'S NO WAY TO FIX unless you do a complete rebuild / reinstall after you do a massive sort through everything that is "missing" (from the pkgdb, that is). Q2. Not with a corrupt / incomplete pkgdb... Chris Rees-2 wrote > Mixing versions with binary packages is a bad idea anyway. Packages are > built with a certain set of dependencies, and you can't mix and match. I only do this when a port build breaks. Say you are building www/foo and build for the depend net/boo breaks or just does not compile. I add net/boo (without any depends) from package and continue with the compile. Or at least I used to be able to do this - Now I no longer can because of pkgng's flag limitations. @Jeffrey Bouquet: AFIK, pkg_add will not register the added package on pkgng's pkgdb sqlite database - you must use pkgng's *pkg add* command for that. You can't even add the same version of a package that was fetched before through the old pkg command through pkgng's *pkg add*. This is because pkgng packages have mysqldb headers included in the file and pkgng must use those headers in the file to properly register it in the db. Even the file endings are different: .tbz vs .txz. IN ESSENCE: I have a corrupt pkgdb for pkgng and there are no apparent fix'em tools useable for pkgng. That means I have to re-build everything! Nice... But too bad that when re-building everything, I no longer have the option of preventing the install of a number of ports listed as dependency but which I absolutely do not want. P.S. Thanks at least for not asking - "why do you not want that port"? or "what's wrong with it"? -- View this message in context: http://freebsd.1045724.n5.nabble.com/pkgng-woes-tp5759489p5759760.html Sent from the freebsd-ports mailing list archive at Nabble.com.