pkgis the preferred name now.
pkg infoshows a list of packages if
pkghas been installed, or offers to install the new package management system if it is not present.
portmaster ports-mgmt/pkgto install the port.
pkg2ngto read the old package database and write the new one. Do that conversion only once.
pkg, can the old pkg_* commands still be used?
pkgcommands are similar, but the
pkgcommand is followed by a space and a subcommand, like
pkgdatabase is a SQLite file called local.sqlite in /var/db/pkg/. The old package database consisted of a subdirectory for each package in this same directory. All of those old subdirectories can be deleted, although portmaster uses them to keep track of things and will recreate them.
make build/install/cleanports commands work fine. Poudriere just makes it possible to build binary packages from ports in bulk.
If I switch, can ports still be used?
Of course. When a port is compiled, it actually creates a package. The package is then installed and managed by the package management system. A binary package is the same, it has just been compiled on a different computer.
When you install a package this is presented to you to confirm installation:However, I might have missed it.
root # pkg install stress Updating local repository catalogue... Fetching meta.txz: 100% 260 B 0.3kB/s 00:01 Fetching packagesite.txz: 100% 139 KiB 142.5kB/s 00:01 Processing entries: 100% local repository update completed. 596 packages processed. The following 1 package(s) will be affected (of 0 checked): New packages to be INSTALLED: stress: 1.0.4 Number of packages to be installed: 1 22 KiB to be downloaded. [b]Proceed with this action? [y/N]:[/b] y Fetching stress-1.0.4.txz: 100% 22 KiB 22.6kB/s 00:01 Checking integrity... done (0 conflicting) [1/1] Installing stress-1.0.4... [1/1] Extracting stress-1.0.4: 100%
pkg info -d blah.1.0and you can list the files in those dependencies
pkg info -l blah.1.0. There's probably a more concise way to do it, but to give you what you want in one command, how about something like
pkg info -d blah.1.0 | cut -d':' -f1 | xargs pkg info -l?
Packages just contain files to be copied to the system. So the information of your desire are in the package where it can be retrieved:I want to know the actual files that are copied to the filesystem
# tar tf /var/cache/pkg/stress-1.0.4-2a6787cc16.txz +COMPACT_MANIFEST +MANIFEST /usr/local/bin/stress /usr/local/man/man1/stress.1.gz /usr/local/share/licenses/stress-1.0.4/catalog.mk /usr/local/share/licenses/stress-1.0.4/LICENSE /usr/local/share/licenses/stress-1.0.4/GPLv3 /usr/local/info/stress.info
Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Checking for upgrades (2 candidates): 100% Processing candidates (2 candidates): 100% Checking integrity... done (0 conflicting)
portsdb -uand on new installs
portsdb -U. I also see in the manual
portsdb -Fand says it is faster than -U, so I guess on a new ports install that I would be better off doing thee -F.
pkgdb -Fto fix duplicated origins. When it happens I end up having to read docs that come with the ports tree version. What exactly are duplicated origins, and why are they not resolved before ports trees are released?
pkg_info –rR. Since you wouldn't necessarily need to have ports installed, are these two commands pulling their information from two different sources to determine dependencies?
pkg_infoat all any more, it is obsolete.
That tells port upgrade to check and update dependencies and depends on.No idea what -rR does with portupgrade
Ah, I remember the old "pirate" option: -arR.That tells port upgrade to check and update dependencies and depends on.
That is currently a loaded question. I use ports-mgmt/portmaster, which, according to some, is the most evil thing possible. Yet it still works. Other people use binary packages from the FreeBSD package repository withWhich tools are the best in your opinion for maintaining ports with FreeBSD 11?
pkg, and that can be adequate. Still others set up their own package builders locally, essentially doing the same thing the FreeBSD package repository does, but allowing them to have their own binary packages with customized options.