From owner-freebsd-ports@FreeBSD.ORG Thu Jan 16 09:32:59 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 80260EF3 for ; Thu, 16 Jan 2014 09:32:59 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 10B391194 for ; Thu, 16 Jan 2014 09:32:58 +0000 (UTC) Received: from mandree.no-ip.org ([78.49.81.108]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0Lh7sF-1VWqX7146x-00oUlO for ; Thu, 16 Jan 2014 10:27:46 +0100 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id DE55323CE92; Thu, 16 Jan 2014 10:27:44 +0100 (CET) Message-ID: <52D7A610.7010800@gmx.de> Date: Thu, 16 Jan 2014 10:27:44 +0100 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: ports vs. new pkg tool (was: Qpopper Port) References: <234AA4B5-BAEB-4067-99FC-5AA803033B6C@lafn.org> In-Reply-To: <234AA4B5-BAEB-4067-99FC-5AA803033B6C@lafn.org> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:ri51T5pjKF0UHIyklxG79JMw+LACwzmTLOCVS5JSvx8KXYBEv55 LlqjAxK45/Zn1dUQd3ipDosLT1rgZrYr7YYPPWScrn091fsPC/cQFbuZcHHNXnDI5uqucff iUEplY1vXBcL/9FJMVLN9winNoKgz1Q6E7BatvjbfJXvd1ZdQ3KYn+IHlZ1mgSRnoBv46Zg mllbnLsqFENQCvrsfJ8+w== Cc: bc979@lafn.org, Bryan Drewery X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jan 2014 09:32:59 -0000 [Bryan, perhaps the pkg-message for portmaster needs revision. Look for occurrences of your name in this message.] Am 16.01.2014 01:08, schrieb Doug Hardie: > I am going to have to give up maintaining qpopper. Not because I > don't have the interest or time, but because I simply cannot update > any port. The old port system may have had issues, but it worked!!! Doug, I have been running pkg on some of my computers, and not run into a road block like you did. > I tried portmaster qpopper to get the latest source. That failed > with lots of errors in other ports. Too many to try to do > individually. In some cases, tools alone cannot fully upgrade the ports on your system, and the /usr/ports/UPDATING file lists changes, sorted by date (newest first) and qualified with port origins, that you must do MANUALLY for a successful upgrade. I suspect your first... > I then used pkg_delete to delete all ports. Repeated > portmaster qpopper. Portmaster no longer exists. Tried pkg_add -r > portmaster. Message to setsomething in /etc/make.conf. Did that and > then tried to run pkg2ng as it requested. pkg2ng does not exist. > Its not a port either. Dead end. Went to > /usr/ports/port-mgmt/portmaster and did a make. Get errors that file > names are misspelled. ...portmaster run bumped into such an obstacle described in /usr/ports/UPDATING and started failing. It is portmaster's policy to first upgrade all requisites, and then the package you want upgraded. But note that the message you got from installing portmaster starts "If you want to switch to the new pkg(8) format," -- if you can answer that for yourself with "no", you can safely ignore the remainder, about the WITH_PKGNG in make.conf (or remove that again), and use portmaster as before. Bryan, portmaster's pkg-message is a non-starter in case the pkg tools are not yet installed, and should mention - on systems that do not ship pkg - that before the user can run pkg2ng, he would need to install the ports-mgmt/pkg port. Doug, if you want to make the switch, pkg2ng is part of the ports-mgmt/pkg package, and only once you install and run pkg2ng is that particular computer sold on running the new pkg tools. Typing "pkg" as a command should present you with a query whether you want to install the pkg tools, with a default of "no", I get this: | $ pkg | The package management tool is not yet installed on your system. | Do you want to fetch and install it now? [y/N]: > Perhaps the new port system can be used by those who spend their day > using it, but for those of us who have real work to do and only use > it when needed, its just not viable. The idea is that the pkg tool makes that easier, and ultimately "pkg upgrade" would fetch signed binary packages from the project for a quicker upgrade, or "pkg install PACKAGENAME" installs PACKAGENAME from a signed binary package that gets downloaded. pkg is new and thus has a few rough edges, but for me, the traditional ways still work.