New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8.7.1 shell completions scripts no longer built and installed by default #13255
Comments
Shell completions weren't being built at all before #13030 (like ver. 8.6.0) so that patch didn't change that. What version were you running where it happened by default? |
The previous maintainer started installing shell completions in 2016-01 curl 7.47.0 without any config changes: |
Please share the build steps that resulted in the shell completion files being
created in the past, because I think there was something special being done to
create them. A standard autoconf build wouldn't have done it it. Now, they
*will* be created when the flag(s) are given.
|
As I said, it looks like the previous curl maintainer added |
That makes perfect sense now. curl now does that itself, but to keep
compatibility with what happened before (no completion scripts by default), you
need to enable the flags to get them created/installed.
|
Thanks, I am playing around changing that build, to see what I can remove of stuff added in earlier releases, hopefully including that. |
I don't consider this a bug. Add the options to the configure like to get them installed. |
These used to be installed by default, but upstream changes now require passing extra flags to `configure` to make sure that they are installed. See curl/curl#13255. Fixes #170210.
I did this
I expected the following
shell completion scripts built and installed
but build now seems to default to NO shell completion scripts, those files were not created, and I had to add configure options:
to get shell completion scripts built and installed.
curl/libcurl version
operating system
CYGWIN_NT-10.0-19045 ... 3.5.1-1.x86_64 2024-02-27 11:54 UTC x86_64 Cygwin
The text was updated successfully, but these errors were encountered: