Update fxp.yaml

[ahmedshahein]

Minor bug fix in the DESCRIPTION file to resolve installation path using "pkg install -forge fxp" by appending the correct path instead of always using 1.0.1 in the installation path.
Release 3.0.0 had major updates:
Added comprehensive help, “help fxp.
Added self-checking testing based on 28 tests, “test fxp”.
Bug fix in rounding scheme “fix – round towards zero”.

[mmuetzel]

Looks good to me. 👍
And all checks in the CI seem to have passed.

[ahmedshahein]

Great!
Many thanks.
Quick question, I want to upload Python and SystemC scripts for comparison against the Octave Class. What is the best way to do that? Shall I create a dedicated repo for that or is there is a certain folder that I can add to the current repo and upload these scripts into it?
Regards

[mmuetzel]

I'm not sure if I correctly understand your question.
In general, everything in the repository that exists at the commit with the tag is part of the tarball that GitHub creates for that tag. So, if your question is whether there are any folders that won't be included in the tarball that pkg install will download, the answer is: No, there are no such "special folders".
However, you could manually upload release assets in which you could omit these folders in a manually created tarball. In that case, you won't be able to use simple tags for your releases. But you'd need to use the "release" feature of GitHub.

Afaict, only the content of some folders is installed as the package for the user locally by default (unless you are using a Makefile). So, if your question is whether it is possible to not install some files that are part of the release tarball of your package, the answer is: Just put them into any folder that isn't named inst, src, doc, or bin.

See also the documentation for the creation of Octave packages: https://docs.octave.org/v11.1.0/Creating-Packages.html#Creating-Packages

Overall: If these files aren't meant to be used by an Octave user installing your package with pkg install, it might be best to keep them in a separate repository to make your life easier when it comes to creating release tarballs and keeping that tarball at its minimum required size.