Extra field in rvload2?

I am reading in the documentation (maybe not where I should look?) the explanation of the rvload2 file format. However, it lists 8 fields per line where as my auto-generated rvload2 file has 9 fields instead, as highligthed below:


Does anyone know what this float/version number may mean, and where does it come from? Thanks in advance.


Reading the source code, it looks like:

  1. Name
  2. Package
  3. Menu
  4. Shortcut
  5. Event
  6. Loaded
  7. Active
  8. RV Version
  9. Optional
  10. (Requires if specified)

So In RV 4+ it appears that the number is the minimum version of RV that is required to run the package. If you check out the PACKAGE file for the associated package, does the value for the rv key exist?

When a package has a greater version number than the version of RV you are running, the package will not be loaded.


Thanks @Michael.Kessler, that was it, indeed the rv key is there. Dealing here with a classic case of undocumented in-house piece of software created by developers who left long ago… :sweat_smile:

1 Like

Of course! Sorry, we’ve all been there.

At the same time, I’m sorry this wasn’t documented up in RV. It looks like it was added to help transition between versions where packages weren’t expected to be able to be loaded in an older version.

At the same time, do note that if you are refactoring, using the rvpkg command-line tool can handle most functions you might need, but if this is a targeted change, it probably isn’t worthwhile to move over :).

Yes, we’ll eventually have to revisit the deployment process, but I will leave that for another thread, if we struggle with it. Thanks again!

1 Like