From owner-freebsd-current@FreeBSD.ORG Tue Nov 4 05:50:57 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 08753552 for ; Tue, 4 Nov 2014 05:50:57 +0000 (UTC) Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B3D37242 for ; Tue, 4 Nov 2014 05:50:56 +0000 (UTC) Received: by mail-ig0-f178.google.com with SMTP id a13so6016623igq.11 for ; Mon, 03 Nov 2014 21:50:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=XW51h1M6gSTIaCAuaLphJ4WpNc949QCG4G+8oQbNvvY=; b=VbP9bM/zDhGTTMBWhc0R3JiN4rRynK2HF58gsu5SCJfnOmnM7k6A/GACMoPJwr4Vi2 gdwaReaO/XqeGMJWeYIY2eipjxd+pfNgFv9j81+tIn15d63buuQa0GF0IrWkRKj9SqSy lnBeUzsgFVIcTNUJhDJ29KSdU/nrycZwbJxsORuzsgjxcFwDxUrR0Fr7/t6wBzxih0mt lY5N5qKbv7a8TApXx34qAEAHBK5uvfDquJfYzyjHtKMpYYbwfqlZAU8Izb9Ru5isT6gO LxXuEBEprkEBPiyXFeE3SgLhJ+VuY7Au/H+ZFOr9TVkPEKNGx9SRXEkYzxr880ycF8We 4Gsg== MIME-Version: 1.0 X-Received: by 10.43.90.198 with SMTP id bj6mr44720275icc.4.1415080255933; Mon, 03 Nov 2014 21:50:55 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.107.11.152 with HTTP; Mon, 3 Nov 2014 21:50:55 -0800 (PST) In-Reply-To: References: <20141028231933.GG26796@ivaldir.etoilebsd.net> <20141101161332.b9c8fc19bf9fc54f73bc5c00@gmail.com> <20141101224549.GG15967@ivaldir.etoilebsd.net> <20141102102455.30d42f85ff81e079788eae06@gmail.com> <5457F64F.6090408@selasky.org> Date: Mon, 3 Nov 2014 21:50:55 -0800 X-Google-Sender-Auth: boQnQ0WgmA6eE0AGeNXtlC4o-f8 Message-ID: Subject: Re: pkg 1.4 freeze please test test test! From: Kevin Oberman To: Henry Hu Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Hans Petter Selasky , Freddie Cash , "current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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: Tue, 04 Nov 2014 05:50:57 -0000 -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.comOn Mon, Nov 3, 2014 at 5:09 PM, Henry Hu < henry.hu.sh@gmail.com> wrote: > On Mon, Nov 3, 2014 at 4:48 PM, Freddie Cash wrote: > > > On Mon, Nov 3, 2014 at 1:40 PM, Hans Petter Selasky > > wrote: > > > > > Is it possible when upgrading a system via "pkg" to selectivly switch > > > upgrades ON/OFF. For example I have a custom ffmpeg install and would > > like > > > to keep it every time I do a binary upgrade? > > > > > > > > > =E2=80=8B# man pkg-lock > > > > ;) > > > > I believe that's what you are looking for.=E2=80=8B No idea how well i= t works > > long-term, though, or if you lock a large number of packages. > > > > I also use pkg-lock, but it has several problems: > * You may miss updates. They are skipped during pkg upgrade > * "xxx is locked and may not be modified" is displayed every time you do > something like pkg upgrade. If you have multiple pkgs locked, it may be > annoying. > > It would be easier to update the pkgs by having something like portmaster > -P. > -- > Cheers, > Henry I simply do periodic(8) weekly runs of "pkg version -vRl\<" to catch any port that has not been updated due to being locked. On option to only report locked packages would simplify this and looks to me like it would be pretty easy to add, but unless you have a lot of locked packages, it's not a problem. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com