jronald, pkg's typically lag behind ports so ... ehrm .. yes and no.
I suppose it depends on how fast a pkg is created from an updated port.
What are you seeing?
pkg update
first. make install
, it'll also make install
its dependencies, but how to make clean
for the dependencies? It's hard to find them out. And do make clean
in /usr/ports is not efficient, it checks every port.It depends. By default a -RELEASE version will use a quarterly branch for packages. These are created once every three months and only updated for security or stability issues. Ports are a "rolling release", i.e. they are constantly updated. There are quarterly branches for ports too but you will need to use Subversion, you can't get them with portsnap(8). There can be big version differences between a quarterly and a latest branch.does pkg and ports have the same version for each package?
What if both pkg or ports are latest?It depends. By default a -RELEASE version will use a quarterly branch for packages. These are created once every three months and only updated for security or stability issues. Ports are a "rolling release", i.e. they are constantly updated. There are quarterly branches for ports too but you will need to use Subversion, you can't get them with portsnap(8). There can be big version differences between a quarterly and a latest branch.
Packages are built every few days I believe, I honestly don't know what the current schedule is. But everything starts with a port, so ports are always the most up to date. Packages can lag a few days until a new package build run is done.What if both pkg or ports are latest?
Packages are built every few days I believe, I honestly don't know what the current schedule is. But everything starts with a port, so ports are always the most up to date. Packages can lag a few days until a new package build run is done.
The pkg's update follows the ports' update so quickly, and pkg must try to choose the most preferrable configure, so its good for common use, especially with relatively small disk space pkg is preferred. ports is more advanced, I'll learn & try it out. Thanks.So depending on when a Port update is committed, and depending on how long the already queued Ports take to build, my guess/experience is that a Package can be a 2-4 days behind the Port (possibly give or take a day).
Packages are always built using the port's default options. This is the main reason why you shouldn't mix ports and packages. The only reason to build from ports is because you want to deviate from the default options. As packages are built using the defaults you can get a difference in dependencies (PortA, with custom options, depends on PortB but PackageA; built from a default PortA; depends on PackageC).pkg must try to choose the most preferrable configure
Yes and no.After# pkg update
&&# portsnap fetch update
, does pkg and ports have the same version for each package?
$ pkg info -rx samba
samba46-4.6.16_1:
fusefs-smbnetfs-0.6.1_1
squid-4.3_1
mplayer-1.3.0.20180920_2
kodi-17.6_7
root@psi:/ # pkg search -dx smbnetfs
fusefs-smbnetfs-0.6.1_1
Comment : Mount smb shares (Fuse filesystem)
Depends on :
fusefs-libs-2.9.9
samba47-4.7.12
glib-2.56.3_2,1
gettext-runtime-0.19.8.1_2
It means pkg keep integrity for itself, and port fit the current system, ok.A port gets build based on your system whereas a package got build with default settings.