70a20866f8
This update changes how python plugins are handled. Previosuly, we linked directly against python, requiring all vim installations to have a dependency on python. Perhaps that's fine for flavours like gtk20 and gtk30, but it's burdensome and often unexpected for TUI users. Now, we use dynamic loading of python libraries, which means that vim should automatically support python plugins if python is installed. If python is NOT installed, no harm/no foul, just no python plugin support. I'm not expecting this to cause any issues, but if it does please reach out!
23 lines
843 B
Plaintext
23 lines
843 B
Plaintext
[
|
|
{ type: upgrade
|
|
maximum_version: "9.0.0129"
|
|
message: <<EOM
|
|
Vim no longer installs or reads a system-wide vimrc. The only overridden
|
|
defaults are those which provide FreeBSD-specific settings. Read through
|
|
$VIMRUNTIME/defaults.vim to see Vim's defaults, and see ':h initialization'
|
|
for the standard locations Vim looks for configuration files.
|
|
EOM
|
|
},
|
|
{ type:upgrade
|
|
maximum version: "0.9.1627"
|
|
message: <<EOM
|
|
The Vim port no longer brings in python automatically. Instead, it is
|
|
a dynloadable feature that can be enabled at runtime by installing python.
|
|
|
|
# pkg add python3
|
|
|
|
It will ONLY work with the version of python that the port was build with
|
|
(i.e. the defualt python version). If you've changed it manually, and want
|
|
python plugin, then you'll need to build and install the port locally.
|
|
]
|