From owner-freebsd-current@FreeBSD.ORG Mon Nov 10 07:54:06 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9EA5CC1C for ; Mon, 10 Nov 2014 07:54:06 +0000 (UTC) Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (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 70EC4B81 for ; Mon, 10 Nov 2014 07:54:06 +0000 (UTC) Received: by mail-ig0-f182.google.com with SMTP id hn18so8652742igb.15 for ; Sun, 09 Nov 2014 23:54:05 -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=Hml93ziHmDclI2LZ+BtEHip194jcGPB85pVwTGUDpYw=; b=sIspB5wPffiouKrajjGN1xG3yIekABcEKCLpG1ZOhqYlzPPgRJzlVS+i4CCax90bEa xshPVAQ0DwZ9SVdYwiFA9ViOJu+gsjHHrSCQq+aj//U9ydQC3oD8xALAJVe2K0l5bRc8 b6P8EmwTVEdlNj22FrIfGxJB/UJqupn1rWoN+GeYe9uY9bvI2y9LLDo5bdwWmc+r8aFR rNzq9hefJNdpNygS8h6yFb2GMY3yKtUGY/B2GBjbMYhTEntn4RwpOwXl4ThWjdZHuqhe DaVtbKnjmLnna0zEtL4oaUixAi/GWELFAl/08xFn7p07d5wZPiPqc/O/03U6vYaJI/NT 7oMw== MIME-Version: 1.0 X-Received: by 10.42.126.196 with SMTP id f4mr167022ics.91.1415606045791; Sun, 09 Nov 2014 23:54:05 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.107.11.152 with HTTP; Sun, 9 Nov 2014 23:54:05 -0800 (PST) In-Reply-To: <54606CB9.4070305@gmx.de> References: <20141028231933.GG26796@ivaldir.etoilebsd.net> <20141101161332.b9c8fc19bf9fc54f73bc5c00@gmail.com> <20141101224549.GG15967@ivaldir.etoilebsd.net> <20141102102455.30d42f85ff81e079788eae06@gmail.com> <5457F64F.6090408@selasky.org> <54606CB9.4070305@gmx.de> Date: Sun, 9 Nov 2014 23:54:05 -0800 X-Google-Sender-Auth: 9WvGQTIk53xH8P_TOrIUExJ814A Message-ID: Subject: Re: pkg 1.4 freeze please test test test! From: Kevin Oberman To: Matthias Andree Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Current 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: Mon, 10 Nov 2014 07:54:06 -0000 On Sun, Nov 9, 2014 at 11:43 PM, Matthias Andree wrote: > Am 03.11.2014 um 22:48 schrieb Freddie Cash: > > 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. > > It used to refuse portmaster upgrades of a locked port and was thus > useless for mixed binary packages + portmaster use. I haven't yet > checked if pkg 1.4 has fixed this. > I don't think that this is considered to be a bug, so it is not fixed. Easy work-around: pkg unlock PACKAGE portmaster PACKAGE pkg lock PACKAGE Personally I would prefer if portmaster did the unlock and lock, perhaps tied to an option, but it's not a big issue as far as I can see. Just an annoyance. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com