Can we have casks for major versions? (for example - dotnet-sdk6)

[RonAmihai]

I'm trying to install both dotnet latest (official cask) & 6 on my macOS, in such a way I'll receive homebrew updates for both without upgrading the dotnet 6 installation to version 7+.

For example - if dotnet 6.0.303 is installed, and I'm running an upgrade, I want it to upgrade to dotnet 6.0.404 and not to dotnet-7.0.101. But still I want to have the official dotnet-7.0.101 cask installation seperately.

Can we have major versions cask for that porpuse? AKA dotnet-sdk7, dotnet-sdk6, dotnet-sdk5, etc.

[isen-ng]

Hello,

In your example, you described that when having installed the dotnet 6.0.xxx cask, and when you upgrade, you don't want the installation to become a dotnet 7.0.xxx cask.

Assuming you are using brew upgrade, this is already the case. Upgrading a dotnet 6.0.xxx cask cask will not turn it into dotnet 7.0.xxx cask. These 2 versions are different casks.

In fact, you can install these 2 casks side by side.

On Thu, Dec 22, 2022, 3:57 PM Ron Amihai @.***> wrote:

I'm trying to install both dotnet latest (official cask) & 6 on my macOS, in such a way I'll receive homebrew updates for both without upgrading the dotnet 6 installation to version 7+.

For example - if dotnet 6.0.303 is installed, and I'm running an upgrade, I want it to upgrade to dotnet 6.0.404 and not to dotnet-7.0.101. But still I want to have the official dotnet-7.0.101 cask installation seperately.

Can we have major versions cask for that porpuse? AKA dotnet 7, dotnet 6, dotnet 5, etc.

— Reply to this email directly, view it on GitHub https://github.com/isen-ng/homebrew-dotnet-sdk-versions/issues/243, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA5ZEK2WGCMLOKALIBVRS5DWOQCWRANCNFSM6AAAAAATGNZC3Q . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[RonAmihai]

Hello, In your example, you described that when having installed the dotnet 6.0.xxx cask, and when you upgrade, you don't want the installation to become a dotnet 7.0.xxx cask. Assuming you are using brew upgrade, this is already the case. Upgrading a dotnet 6.0.xxx cask cask will not turn it into dotnet 7.0.xxx cask. These 2 versions are different casks. In fact, you can install these 2 casks side by side. … On Thu, Dec 22, 2022, 3:57 PM Ron Amihai @.> wrote: I'm trying to install both dotnet latest (official cask) & 6 on my macOS, in such a way I'll receive homebrew updates for both without upgrading the dotnet 6 installation to version 7+. For example - if dotnet 6.0.303 is installed, and I'm running an upgrade, I want it to upgrade to dotnet 6.0.404 and not to dotnet-7.0.101. But still I want to have the official dotnet-7.0.101 cask installation seperately. Can we have major versions cask for that porpuse? AKA dotnet 7, dotnet 6, dotnet 5, etc. — Reply to this email directly, view it on GitHub <#243>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA5ZEK2WGCMLOKALIBVRS5DWOQCWRANCNFSM6AAAAAATGNZC3Q . You are receiving this because you are subscribed to this thread.Message ID: @.>

Indeed, but I still want the 6.0.xxx cask to upgrade to the latest 6.0.xxx version, and not remain the same.

My purpose Is to keep up-to-date dotnet-sdk6 installation, If you've got my point. Sort of creating a dotnet-sdk6.rb cask, and updating it's info every time a dotnet 6 patch/update comes out. The same applies to other major versions of course

[isen-ng]

I'm sorry, I am confused on what you want.

In your first sentence, you asked to 6.0.xxx cask to upgrade to the latest 6.0.xxx version, and in your second paragraph, you're asking for 6.y.xxx cask to upgrade to the latest 6.y.xxx version.

Your first sentence's use-case is already working today. For your second paragraph's use-case, personally, I don't see much utility in providing a cask for dotnet6. When there is already a dotnet7, this means that there won't be new updates to dotnet6, except for bug fixes. This means that there will not be any minor updates. There will only be patch updates. This means that there is almost no need to install another dotnet6.y cask.

On the flip side, introducing another set of casks for dotnet6 and dotnet7 introduces extra complexity and brings extra confusion to users who are not as savvy. I would like to avoid that.

[isen-ng]

Closing until there is renewed interest