After install py27-google-compute-engine: 2.8.13_3 (installed default freebsd-13-0-current-amd64-v20190425) :~ # ls -la /usr/local/bin/google_* -rwxr-xr-x 1 root wheel 465 Apr 26 14:57 /usr/local/bin/google_accounts_daemon-2.7 -rwxr-xr-x 1 root wheel 469 Apr 26 14:57 /usr/local/bin/google_clock_skew_daemon-2.7 -rwxr-xr-x 1 root wheel 463 Apr 26 14:57 /usr/local/bin/google_instance_setup-2.7 -rwxr-xr-x 1 root wheel 479 Apr 26 14:57 /usr/local/bin/google_metadata_script_runner-2.7 -rwxr-xr-x 1 root wheel 463 Apr 26 14:57 /usr/local/bin/google_network_daemon-2.7 services not run :~ # service google_accounts_daemon status /usr/local/etc/rc.d/google_accounts_daemon: WARNING: cannot read shebang line from /usr/local/bin/google_accounts_daemon google_accounts_daemon is running as pid 652. py36-google-compute-engine-2.8.13_3 set correct simlinks lrwxr-xr-x 1 root wheel 26 Apr 27 21:48 /usr/local/bin/google_accounts_daemon -> google_accounts_daemon-3.6 -rwxr-xr-x 1 root wheel 465 Apr 27 21:48 /usr/local/bin/google_accounts_daemon-3.6
Hi, I was able to reproduce what you reported, and after some investigation I found out what is happening. The problem is that the symlinks are only created in the package when its flavor (py27, py36) matches with the default python version. For instance, if you set `DEFAULT_VERSIONS= python=2.7` in /etc/make.conf and try to build/install the py27-google-compute-engine, it will have the symlinks in place. In this presented scenario, the py36-google-compute-engine will not have the symlinks. So I think this is not a bug, it's an expected behavior. Set the default python version you want to use in /etc/make.conf and everything will work fine.
I'm have this test freebsd-13-0-current-amd64-v20190425 in Google Cloud Platform. Without customization, with standard repo FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest",
This was fixed in ports r501547 and you won't see it if you use freebsd-13-0-current-amd64-v20190524. Unfortunately, there seems to be a new issue with the package: Traceback (most recent call last): File "/usr/local/bin/google_instance_setup-2.7", line 6, in <module> from pkg_resources import load_entry_point File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3241, in <module> @_call_aside File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3225, in _call_aside f(*args, **kwargs) File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3254, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 583, in _build_master ws.require(__requires__) File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 900, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 786, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'boto' distribution was not found and is required by google-compute-engine /etc/rc: WARNING: failed to start google_instance_setup which I guess is related to ports r501581, so I'll take a look and see if I can fix that.
Think this is fixed, see the new bug for that issue.