ports and packages installed on one system, how to make pkg only
tech-lists at zyxst.net
Thu Sep 26 16:29:36 UTC 2019
On Thu, Sep 26, 2019 at 04:59:27PM +0100, Matthew Seaman wrote:
>A pkg is what you get from compiling a port. Once the port is installed
>it's a pkg and there's no functional difference from a pkg installed
>from one of the package repositories.
>Or, in other words, just update your machine from the pkg repos. It
>will replace anything that's out of date, no problem. There's no
>particular need to force an update on all packages -- if it's already
>there and working OK, then my inclination would be to leave it be.
What's of particular concern for me is that the machine had this in its
/etc/make.conf when it was building it's own ports:
I've since removed it.
Since then, the machine has been brought to 12R-p10 and I've made a poudriere
instance for it on different hardware which has nothing special in its own
make.conf. I fed it a ports list obtained on the client through
*portmaster --list-origins | sort -u | tee portslist.txt*, transferred that to
poudriere and it built the ports, and all the flavoured python ones were py36-*
So, if I *pkg upgrade -f* on the client (which now knows to use my poudriere
instance), would it be reasonable for me to expect all py27* to be upgraded
to py36*, without stuff breaking?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: not available
More information about the freebsd-questions