From owner-freebsd-ports@freebsd.org Sat Dec 19 16:54:24 2015 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2B340A4CDFF for ; Sat, 19 Dec 2015 16:54:24 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E400F122E for ; Sat, 19 Dec 2015 16:54:23 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 10D5E28426 for ; Sat, 19 Dec 2015 17:54:20 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 35C212842E for ; Sat, 19 Dec 2015 17:54:19 +0100 (CET) Message-ID: <56758BBB.9030804@quip.cz> Date: Sat, 19 Dec 2015 17:54:19 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: Using pkg updating without /usr/ports References: <56755B17.3080904@quip.cz> <20151219134610.GO1173@albert.catwhisker.org> In-Reply-To: <20151219134610.GO1173@albert.catwhisker.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2015 16:54:24 -0000 David Wolfskill wrote on 12/19/2015 14:46: > On Sat, Dec 19, 2015 at 02:26:47PM +0100, Miroslav Lachman wrote: >> Hi, >> I am using own poudriere repo to build needed packages for our server. I >> was used to `pkg_updating` or `pkg updating` in the past (when I was >> compiling ports on each server). >> I don't have /usr/ports on server anymore. So the `pkg updating` command >> doesn't work. (There is no /usr/ports/UPDATING file) >> Is there any standard way to use it without ports tree, just with my own >> poudriere repo? >> .... > > I find that "pkg upgrade" works well for that purpose in my case. > > Note that this implies that /usr/local/etc/pkg/repos/custom.conf > has a pointer to my package repository, and that > /usr/local/etc/pkg/repos/FreeBSD.conf indicates that use of the > FreeBSD.org repository has been disabled -- e.g.: > > bats(10.2-S)[4] cat /usr/local/etc/pkg/repos/custom.conf > custom: { > # url: file:///net/freebeast/local/amd64/local/poudriere/data/packages/10amd64-ports-home > url: file:///mnt > enabled: yes, > } > bats(10.2-S)[5] cat /usr/local/etc/pkg/repos/FreeBSD.conf > FreeBSD: { > enabled: no > } > bats(10.2-S)[6] > > ("bats" being a machine that does not have a /usr/ports, and > "freebeast" being my build machine. The comment for custom.conf > is intended to document that I need to explicitly mount the pkg > repo before accessing it, as bats does not run an automounter (while > another machine that is treated otherwise similarly does run an > automounter, and thus does not need the explicit mount first).) pkg update and pkg upgrade works fine for me too, but pkg updating not. pkg updating is intended to read /usr/ports/UPDATING file and compare its content to installed packages and show important messages before running `pkg upgrade`. But UPDATING file is not automatically synchronised between build server and 'client' (machine where I need to run `pkg updating`). Miroslav Lachman