Current package_tool can use the following JSON to specify a pacakge list on a per-OS type basis

{
  "dependencies": {
     "rhel": ["gcc"],
     "ubuntu": ["gcc"],
     "sles": ["gcc"],
     "amzn": ["gcc"]
   }
}

This works well most of the time, but when some packages get renamed between OS versions we have no way to support this currently.

We should be able to handle this case, something like the following JSON should work well.

{
  "dependencies": {
    "ubuntu": ["gcc"],
    "rhel": {
       "9.6": ["gcc"],
       "9": ["g++"],
       "default": ["gcc"]
   },
...
}

This solution should

• Not break the already established "osname": [<list of packages>] format since it is already in place with a lot of wrappers.
• Support working with full version numbers for one-off releases
• Support working with major version numbers since they are most likely to contain package naming differences
• Support providing a default set of packages when a full version number/major version number does not match the running system

The order of preference should be:

• Full version number
• Major version number
• Default set of packages.