Freebsd – How to tell which of the ports I compiled theself and which I installed from pre-compiled binary packages

freebsd

I have two FreeBSD 10.2-RELEASE systems and I'm trying to set up the second to be almost identical to the first. I don't wish to use ZFS snapshots for this task; I would just like to select, install, and compile the same software versions.

During the installation of the first system I know that I installed some binary ports by using the pkg tool and I also compiled some packages from source with make install clean in the /usr/ports/ hierarchy.

Now when I run pkg info on the first system it shows me both of these types. I'd like to know if there is any way that I could differentiate which were compiled from source, without looking back through my shell history.

I have found out that I can do pkg query -e '%a = 0' %o to find non-automatically installed packages, which must then be those that I have selected, but I still can't quite tell which I compiled from source.

Many thanks.

Best Answer

You can play with repository (%R). First try:

pkg query "%R %o" | grep unknown

Of course you can filter with awk (awk '/unknown/ {print $2}') or sed.

Related Solutions

FreeBSD: Mixing packages and ports

You can use ports and packages simultaneously, both use the same package database in /var/db/pkg.

Actually, packages are generated by the ports system. For example, make package will install a port and generate the binary package for it. Also you can create a package from the currently installed port with the pkg_create -b command.

Freebsd – How to deal with FreeBSD’s move to pkgconf

You should always read /usr/ports/UPDATING before carrying out a port upgrade. In this case, it has this to say about the deprecation of pkg-config:

20120726:
  AFFECTS: users of devel/pkg-config
  AUTHOR: bapt@FreeBSD.org

  devel/pkg-config has been replaced by devel/pkgconf

  # portmaster -o devel/pkgconf devel/pkg-config
  or
  # portupgrade -fo devel/pkgconf pkg-config-\*

  pkgng:
  # pkg set -o devel/pkg-config:devel/pkgconf
  # pkg install -f devel/pkgconf

If you follow these instructions, your ports management tool of choice (which seems to be portmaster in your case) will remove pkg-config and install pkgconf, and will update the package registry database under /var/db/pkg to reflect the change. If you were a portupgrade user, the upgrade would also fix up the dependency graph in portupgrade's own database, which is separate from the standard registry.

Future installs/upgrades should "just work".

Best Answer

Related Solutions

FreeBSD: Mixing packages and ports

Freebsd – How to deal with FreeBSD’s move to pkgconf

Related Question