[Bug 245667] [feature request] ports-mgmt/pkg: Determine ports branch of active pkg repo

From: <bugzilla-noreply_at_freebsd.org>
Date: Sun, 02 Jan 2022 15:09:05 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245667

Ian Jefferson <ijeffsc@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ijeffsc@gmail.com

--- Comment #6 from Ian Jefferson <ijeffsc@gmail.com> ---
For what it's worth...

I've been using FreeBSD for a long time since Version 4 or perhaps V3.

I always assumed that packages and ports were linked automatically and that any
dependency issues were just a bug.

I ran across this bug report via a thread Jason started in the ports and
packages forum and I found that thread after reading in the beloved handbook
that if I wanted to use both ports and packages then I had to ensure they were
working from the same branch.  I quote:

"If the Ports Collection and pkg must be used in conjunction, then be sure that
your Ports Collection and pkg are on the same branch release of the ports
tree."

In fact it would be a trivial system indeed that did not absolutely require
both systems - it is one of the great features of FreeBSD.

9/10 times a package will suffice and using packages for install is far faster
than ports so it is compelling to go that way so most of my little server
installs indeed use packages now though I started with only ports.   

Only a trivial server with limited services would not require some kind of
modification to one of the package default compile options.   This seems to be
a trend (i.e. the notion of a VM or Container so support a single application)
but there are still little servers like mine that support quite a variety of
services like an old mainframe and do it quite well.    

It would be a shame to have to go back to ports only or to have to manually
compile each application outside of a maintained tree.

-- 
You are receiving this mail because:
You are the assignee for the bug.