Update fxp.yaml

[ahmedshahein]

Added comprehensive help, “help fxp.
Added self-checking testing using 28 tests, “test fxp”.
Bug fix in rounding scheme “fix – round towards zero”.

[ahmedshahein]

This is further enhancements and updates.

• Added comprehensive help, “help fxp.
• Added self-checking testing, “test fxp”.
• Bug fix in rounding scheme “fix – round towards zero”.
  I have a remark regarding the installation using the standard "pkg install -forge fxp". I observed that despite it fetches the correct file the installation path is still using the initial file. Despite that I manually removed the folder it still coming back to the old path, as shown below:
  .var/app/org.octave.Octave/data/octave/api-v60/packages/fxp-1.0.1/

Could you please check this issue?
Regards,
Ahmed.

[mmuetzel]

• I have a remark regarding the installation using the standard "pkg install -forge fxp". I observed that despite it fetches the correct file the installation path is still using the initial file. Despite that I manually removed the folder it still coming back to the old path, as shown below:
  .var/app/org.octave.Octave/data/octave/api-v60/packages/fxp-1.0.1/

I'm not sure I correctly understand what you mean. But it looks like you forgot to update the DESCRIPTION file. It still says:
https://github.com/ahmedshahein/pkg-fxp/blob/e07b5b6ec59c228e610c2d82f9ff85609e646eb3/DESCRIPTION#L2-L3

Version: 1.0.1
Date: 2026-01-26

[ahmedshahein]

Accepted suggestions of stating on the minimum (least) tested tool version.

[mmuetzel]

If you don't mind the wrong version being reported, e.g., for pkg list, we could merge the update as-is.
Otherwise, you should fix the DESCRIPTION file in your repository and prepare a new tarball for your package.

Please, let us know how you'd like to proceed.

[ahmedshahein]

Hi,
I have just updated the DESCRIPTION file as advised.
Thanks

[mmuetzel]

Should we wait for you to update the 3.0.0 tag in your repository (and update the checksum in this PR accordingly)? Or do you prefer to make the release with the tarball before that change (i.e., with the version mismatch)?

[ahmedshahein]

The tag (3.0.0) and the checksum was already updated before I initiated the review. Do I need to regenerate the checksum for any reason?

[mmuetzel]

The tag (3.0.0) and the checksum was already updated before I initiated the review. Do I need to regenerate the checksum for any reason?

You wrote that you fixed the version and date in the DESCRIPTION file in your repository. But that was after you created this PR. Hence, that change wouldn't be part of the version that users would be installing in Octave with pkg install fxp if we were to merge this PR as-is.
That is why I asked you whether you would like to move the tag in your repository to a commit that includes the changed DESCRIPTION file.

[ahmedshahein]

Oh, okay, I understood now.
I prefer to make a new release then with all these fixes. Will do it today.

[mmuetzel]

Closing this PR in favor of #735.