[octave] add new port

[talregev]

• Changes comply with the maintainer guide.
• The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
• Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx.
• The versioning scheme in vcpkg.json matches what upstream says.
• The license declaration in vcpkg.json matches what upstream says.
• The installed as the "copyright" file matches what upstream says.
• The source code of the component installed comes from an authoritative source.
• The generated "usage text" is accurate. See adding-usage for context.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is in the new port's versions file.
• Only one version is added to each modified port's versions file.

[dg0yt]

Just first feedback.
Too early to decide on spending more time on this PR.

[dg0yt]

This disables all vcpkg CI coverage.

[talregev]

I know, but I only succeeded to compile this port with vcpkg on dynamic ubuntu.

[MonicaLiu0311]

This is not allowed for the following reasons:

1. Currently, the official Linux we support is statically built. Your expression will cause our CI to be unable to detect and run. triplets/x64-linux.cmake:

set(VCPKG_TARGET_ARCHITECTURE x64)
set(VCPKG_CRT_LINKAGE dynamic)
set(VCPKG_LIBRARY_LINKAGE static)

set(VCPKG_CMAKE_SYSTEM_NAME Linux)

2. I found that the upstream supports windows & linux & osx. In this case, "support" should be consistent with the upstream. You can write the failed triplets into ci.baselin.txt:
   

[talregev]

Just first feedback. Too early to decide on spending more time on this PR.

I admit that needed more work to compile this port on more triplets.

[MonicaLiu0311]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[MonicaLiu0311]

Ping @talregev

[talregev]

@MonicaLiu0311 Thank you for your review.
I will take a look and I will respond

[talregev]

@MonicaLiu0311
On the build system itself it say it cannot build with static:
https://github.com/gnu-octave/octave/blob/3fedbfc38b3f06f1ade3db4b0f011191a18b9f92/configure.ac#L637

[talregev]

@MonicaLiu0311 On the build system itself it say it cannot build with static: https://github.com/gnu-octave/octave/blob/3fedbfc38b3f06f1ade3db4b0f011191a18b9f92/configure.ac#L637

I will try to patch and remove this error and see what will happen.

[dg0yt]

After reading the issue mentioned in configure.ac, it seems that this port os a candidate for

vcpkg_check_linkage(ONLY_DYNAMIC_LIBRARY)

[talregev]

Revert the port to be non static.
Wait all the ci that will fail, then I will add it to ci.baselin.txt

[MonicaLiu0311]

@talregev Is there any new progress?

[talregev]

for me, I finished develop this port.
It has only dynamic Linux working.
Should at least dynamic windows work?

If you want to review, go ahead, and let me know what you think.

[dg0yt]

There must be at least one CI configuration which builds the port.
And this is how it could be done: #38243 (comment).

[talregev]

@dg0yt Do you want to try this? You can use my commits.