Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 7 Dec 2015 16:50:10 +0000
From:      Steve O'Hara-Smith <>
Subject:   Re: [Phishing]Re: Migrating to FreeBSD from Debian
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <> <> <> <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Mon, 7 Dec 2015 16:12:43 +0000
Matthew Seaman <> wrote:

> On 2015/12/07 15:54, Daniel Feenberg wrote:
> > What does the warning mean? That once I have installed a single package
> > I can never use ports? So if I want a port, and already have packages, I
> > have to uninstall all of the packages first and can never in the future
> > install any package? That seems extreme. Or is there a less restrictive
> > interpretation that is more correct?
> Usually the reason for mixing ports and packages is because you want
> something compiled with non-default options.
> The difficulty arises when you find that despite all your best
> intentions, you end up with the default package anyhow, or you end up
> installing all the dependencies for the default package and not the ones
> for your customized version, or you end up installing a lot of build
> dependency things you didn't really want.  And then when you go to
> upgrade, it breaks all over again in similar but not exactly the same
> ways.

	pkg lock and make missing are your friends. First step after
deciding a port is a must is to go into the port and make config to set
things up the way you want. Then run make missing and pkg add as much as
possible (this to avoid excessive compiling). Finally pkg lock everything
you had to build because you changed it.

> It's loss of control which is the problem.  You may be lucky in that it
> 'just works' with your customizations, or it may become a nightmare of
> dependency hell from which all right-thinking sysadmins would run away,
> screaming.

	You do need to keep the ports and packages you use in reasonably
close sync - ideally use the ports tree the packages are built from. So
when you upgrade packages also upgrade the ports tree and rebuild the ports.

	There is a script called sync-ports which pulls the right ports
tree - although the version I have doesn't handle 10.2.

	The only time life gets nasty is if you have to customise a
dependency and something else can't live with that customisation. I've
not hit that yet, so far all my needed customisations have been on high
level packages.

Steve O'Hara-Smith <>

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