From owner-freebsd-current@FreeBSD.ORG Mon Jul 23 09:31:07 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00F4E106564A for ; Mon, 23 Jul 2012 09:31:07 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id A98F88FC14 for ; Mon, 23 Jul 2012 09:31:06 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1StEyn-0007hl-Tx>; Mon, 23 Jul 2012 11:31:05 +0200 Received: from munin.geoinf.fu-berlin.de ([130.133.86.110]) by inpost2.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1StEyn-0002Pq-RT>; Mon, 23 Jul 2012 11:31:05 +0200 Message-ID: <500D19EE.7030607@zedat.fu-berlin.de> Date: Mon, 23 Jul 2012 11:31:26 +0200 From: "Hartmann, O." Organization: FU Berlin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120620 Thunderbird/13.0.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <500D0EA5.4050900@zedat.fu-berlin.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Originating-IP: 130.133.86.110 Subject: Re: portmaster and pkgng X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 09:31:07 -0000 On 07/23/12 11:07, Chris Rees wrote: > On 23 Jul 2012 09:44, "Hartmann, O." wrote: >> >> Hello. >> >> I'd like to try pkgng with portmaster. I see that "pkg2ng" is involving >> the directory /var/db/pkg, so this implies that there may implications >> also for usage with ports-mgmt/portmaster. portmaster is supposed to be >> the tool completely dependend on system's toolsets, isn't it? >> >> I know that "pkg" is supposed to be more for binary maintainance of the >> system, but I'd like to be "stuck" with compiling my ports. Is there an >> issue with that? >> >> Thanks inadvance and sorry for the (naive) noise. > > Of course you can stay with compiling your ports directly, but I think > you'll be so amazed with how easy it is to make binary package sets > yourself and use them that you'll use them instead :). You still have all > the advantages of compiling from source. > > http://blog.etoilebsd.net/post/Home_made_pkgng_repo > > Chris Hello Chris. I need to go step by step. I installed ports-mgmt/pkg and did a pkg2ng and watched the folder /var/db/pkg has been backuped and then changed towards the pkgng usage. portmaster now is not recognizing anymore the format of the /var/db/pkg folder - for those considered the knowledged no surprise, for me simply the indication that portmaster usage isn't usable as usual. Well, if I understand it right, pkg is considered to be for binary packages and does not make portmaster obsolete, if I'm inclined compiling my ports myself, am I right? Well, I thought I read in here that pkg has now a much more sophisticated tracking of dependencies - usage of SQLite implies, that there is now a great opportunity of doing well in tracking problems and versioning (I might be wrong). I tried to follow the chat on the list about pkgng, but for the rush I didn't figured out whether portmaster is considered obsolete - I saw patches for portupgrade flushing in, so my logic has been falsified by that implicitely ... Thanks for the link, I'll see what it about, sounds promising ... Regards, Oliver -- Oliver Hartmann Freie Universität Berlin Planetologie und Fernerkundung Malteserstr. 74 - 100/Haus D D-12249 Berlin Tel.: +49 (0) 30 838 70 508 FAX: +49 (0) 30 838 70 539