Base should know the installed version of the command line tools

[ryandesign (Ryan Carsten Schmidt)]

Just as MacPorts already knows the version of Xcode (in the xcodeversion variable), it should know the version of the command line tools. This could then be printed in the log and verified by the configure script as the Xcode version already is.

Per ​this post, this information can be obtained on Mavericks or later using:

pkgutil --pkg-info=com.apple.pkg.CLTools_Executables

e.g.:

$ pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
package-id: com.apple.pkg.CLTools_Executables
version: 9.2.0.0.1.1510905681
volume: /
location: /
install-time: 1514035707
groups: com.apple.FindSystemFiles.pkg-group

---

On Lion and Mountain Lion, it's:

pkgutil --pkg-info=com.apple.pkg.DeveloperToolsCLI

e.g.:

$ pkgutil --pkg-info=com.apple.pkg.DeveloperToolsCLI
package-id: com.apple.pkg.DeveloperToolsCLI
version: 5.1.0.0.1.1396320587
volume: /
location: /
install-time: 1467560350

---

On Leopard and Snow Leopard, it appears to be:

pkgutil --pkg-info=com.apple.pkg.DeveloperToolsCLILeo

e.g.:

$ pkgutil --pkg-info=com.apple.pkg.DeveloperToolsCLILeo
package-id: com.apple.pkg.DeveloperToolsCLILeo
version: 1.0.0.9000000000.1.1248867338
volume: /
location: /
install-time: 1470134505

---

I haven't checked Tiger.

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

There is a ​pull request that creates a port group (cltversion-1.0.tcl) that does what you suggest.
If it works, we can work toward moving it into base.

Based on the discussion in the pull request, it seems to be fairly easy for the command line tools to be installed but for pkgutil to fail.
My best guess is that upgrading Xcode messes with the receipts.
I have added a section ​in the wiki with a description of the problem.

[jmroot (Joshua Root)]

[d05ebde36fa2e2dd36d91aa5693be706c082342f/macports-base]