dotnet: add dotnet 9.0 runtime

[brice-fromentin]

Description

Package with dotnet 9 release.

Fixes #6343

Checklist

• Build rule all-supported completed successfully
• New installation of package completed successfully
• Package upgrade completed successfully (Manually install the package again)
• Package functionality was tested
• Any needed documentation is updated/created

Type of change

• Bug fix
• New Package
• Package update
• Includes small framework changes
• This change requires a documentation update (e.g. Wiki)

[hgy59]

@brice-fromentin do you really need .net 9?
my intention was to create packages for LTS versions only (i.e. version 8, 10, 12, ...)

[mreid-tt]

@brice-fromentin, thanks for your contribution. Looking at #5972, I believe that @hgy59 may prefer a consistent folder naming structure. So rather than having your package folder in spk/ and cross/ called dotnet-9-runtime, perhaps you can use dotnet9-runtime for consistency.

Other than that the notes I left in the Makefile are the only things I picked up that may need addressing.

[brice-fromentin]

@brice-fromentin do you really need .net 9? my intention was to create packages for LTS versions only (i.e. version 8, 10, 12, ...)

Yes there is a lot of benefits on it.

[brice-fromentin]

@brice-fromentin, thanks for your contribution. Looking at #5972, I believe that @hgy59 may prefer a consistent folder naming structure. So rather than having your package folder in spk/ and cross/ called dotnet-9-runtime, perhaps you can use dotnet9-runtime for consistency.

Other than that the notes I left in the Makefile are the only things I picked up that may need addressing.

Thanks for your feedbacks, I update with those.

[mreid-tt]

I notice that you moved the DSM minimum from 7.0 to 7.1. Was there any particular reason for this? What is the primary logic you are using to determine minimum DSM version?

Also, until the package is published there is no need to change the SPK_REV. It should stay as 1 for now.

[brice-fromentin]

I notice that you moved the DSM minimum from 7.0 to 7.1. Was there any particular reason for this? What is the primary logic you are using to determine minimum DSM version?

Also, until the package is published there is no need to change the SPK_REV. It should stay as 1 for now.

Thx for your help, I switched back to 7.0 because there is no real requirements.

[mreid-tt]

@brice-fromentin, my apologies for not catching this earlier. It seems you're making edits directly on the master branch rather than using a dedicated branch. This approach deviates from our standard practice, as it can complicate maintenance, as previously pointed out by @hgy59. You might need to create a new PR following the correct workflow.

EDIT: I recommend saving your modified files, creating a new branch, and moving the modified files into it. Everything else can be copied from this PR.

[brice-fromentin]

@brice-fromentin, my apologies for not catching this earlier. It seems you're making edits directly on the master branch rather than using a dedicated branch. This approach deviates from our standard practice, as it can complicate maintenance, as previously pointed out by @hgy59. You might need to create a new PR following the correct workflow.

EDIT: I recommend saving your modified files, creating a new branch, and moving the modified files into it. Everything else can be copied from this PR.

@mreid-tt , sorry, I do it like that.