Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 7 Jan 2015 02:26:47 +0100
From:      Roman Naumann <>
Subject:   Re: Questions from a Linux refugee
Message-ID:  <20150107012647.GC973@bulldozer.local>
In-Reply-To: <20150107001205.2be44bae@jive>
References:  <20150106115503.4870ab2e@jive> <> <> <20150106175649.GB973@bulldozer.local> <20150107001205.2be44bae@jive>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Wed, Jan 07, 2015 at 12:12:05AM +0100, Lev wrote:
> On Tue, 6 Jan 2015 18:56:49 +0100
> Roman Naumann <> 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,

Want to link to this message? Use this URL: <>