Update README.md - Update build process on FreeBSD 14 #619
Conversation
|
@tinyboxvk I haven't tried these instructions on my end, but assume you did, the changes look reasonable. |
|
Yes, I have. It was on a new FreeBSD 14.1 install with minimal tools pre-installed. |
Remove exact FreeBSD version
| @@ -35,13 +35,13 @@ that it owns or licenses any of the mentioned, nor does it grant them. | |||
| On FreeBSD the following packages are required: | |||
|
|
|||
| ``` | |||
| pkg install py39-pip jpeg-turbo gmake | |||
| pkg install python py311-pip jpeg-turbo gmake | |||
There was a problem hiding this comment.
one last note here is that python may conflict with py311- as one is implicit but all other packages follow the version/ py311-pip should install the right python311 package and avoid the metapackage?
There was a problem hiding this comment.
There is a difference in what packages are installed.
root@freebsd:~ # pkg install python311
...
New packages to be INSTALLED:
libffi: 3.4.6
mpdecimal: 4.0.0
python311: 3.11.10
readline: 8.2.13_1
Number of packages to be installed: 4
...
This does not create python or python3 under /usr/local/bin, so scripts like collect_api_endpoints.py wouldn't run.
root@freebsd:~ # pkg install python
...
New packages to be INSTALLED:
libffi: 3.4.6
mpdecimal: 4.0.0
python: 3.11_3,2
python3: 3_4
python311: 3.11.10
readline: 8.2.13_1
Number of packages to be installed: 6
...
This creates python and python3 under /usr/local/bin, where python is a symbolic link to python3, and python3 a symbolic link to python3.11.
There was a problem hiding this comment.
And just to add, collect_api_endpoints.py for example depends on /usr/local/bin/python3 being available, which is installed by the metapackage.
No description provided.