From owner-freebsd-questions@FreeBSD.ORG  Wed Jan  7 01:26:53 2015
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@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 5A881734
 for <freebsd-questions@freebsd.org>; Wed,  7 Jan 2015 01:26:53 +0000 (UTC)
Received: from mail.hemio.de (mail.hemio.de [176.9.40.240])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1B3F21306
 for <freebsd-questions@freebsd.org>; Wed,  7 Jan 2015 01:26:52 +0000 (UTC)
Received: from bulldozer.local (p4FC24BC4.dip0.t-ipconnect.de [79.194.75.196])
 by mail.hemio.de (Postfix) with ESMTPSA id 02AB21BC
 for <freebsd-questions@freebsd.org>; Wed,  7 Jan 2015 02:26:47 +0100 (CET)
Date: Wed, 7 Jan 2015 02:26:47 +0100
From: Roman Naumann <roman.naumann@fu-berlin.de>
To: freebsd-questions@freebsd.org
Subject: Re: Questions from a Linux refugee
Message-ID: <20150107012647.GC973@bulldozer.local>
References: <20150106115503.4870ab2e@jive>
 <CAOc73CA9nEWSFckf2r1S9eQKWN+za-NKcU_25z1EHyJDdAqPvw@mail.gmail.com>
 <20150106132934.7b2ba08c.freebsd@edvax.de>
 <20150106175649.GB973@bulldozer.local>
 <20150107001205.2be44bae@jive>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150107001205.2be44bae@jive>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jan 2015 01:26:53 -0000

On Wed, Jan 07, 2015 at 12:12:05AM +0100, Lev wrote:
> On Tue, 6 Jan 2015 18:56:49 +0100
> Roman Naumann <roman.naumann@fu-berlin.de> wrote:
> 
> > If it's just one or a few packages, you can lock them with
> > "pkg lock <packagename>". This might prevent upgrades, though,
> > see "pkg help lock" for details.
> > If you cannot upgrade any more, just use "pkg unlock <packagename>",
> > upgrade, reinstall the package and lock it again after that.
> 
> Yes... but then I have to keep track what did I locked. No. Let the
> computer work. I'm an electrical engineer, I want to design schematics,
> PCBs, write software, and I don't want to work for a package management
> system.

I am sorry, but I do not see a more automated solution to this. If it
is not available as a binary package, you have to install from ports
or source. In either case, upgrading scilab's dependencies via binary
packages might break the installation. Therefore the locking.

If you use quarterly package updates you will have to type only few
lines more every now and then.

You do not need to keep track of what you locked either:
"pkg query -e %k=1 %o" shows you.

>From my experience, this is not easier in the Linux world if no binary
package is available - but then again, you said there is one on your
Linux distribution. :-)

Best regards,
Roman