search

Starz0r / ChocolateyPackagingScripts

4 stars 1 forks source link

Update dotnet4.7.2 dependencies #8

Closed rollingmoai closed 1 year ago

rollingmoai commented 2 years ago

This package is deprecated. End users should install the dotnetfx package. Package maintainers should depend on the netfx-4.7.2 package.

Packages that need to be fixed:

Maybe I missed something else, please fix.

Starz0r commented 1 year ago

Looks like tweetdeck no longer relies on .NET Framework 4.7.2, and has moved on to .NET 7. As for omnisharp, they still provide versions using .NET Framework 4, but are moving towards .NET 6. I'm not using the .NET 6 versions of omnisharp, so I will update for those.

Sorry this took so long to implement :(.

rollingmoai commented 1 year ago

All good. I already switched to Winget + Scoop a long time ago due to many cases of outdated packages like this 😅.

Starz0r commented 1 year ago

That's fine, I hope Winget serves you well.

Although, you do mention "outdated" packages, and the packages I manage are usually updated 1-3 days from the time updates are dropped. The issue you originally opened was about the wrong runtime package dependency being listed instead of the right one. Unless this was referring to something else? My packages usually don't stay out of date for too long...

rollingmoai commented 1 year ago

I was referring to something else. Although, in cases like this, it would be easy to PR a fix directly in winget-pkgs over some maintainer's possibly dead repo (not saying yours) or take package ownership (in which case it might be their turn to disappear afterwards).

Starz0r commented 1 year ago

That's understandable. I recently just inherited another dead package from a maintainer who hasn't been around in years. I'm not really sure how it works with Winget, if Microsoft does all the packages then I guess you'll never have to worry (which I assume is the truth).

rollingmoai commented 1 year ago

if Microsoft does all the packages then I guess you'll never have to worry (which I assume is the truth).

Not really. The difference is that all packages are centralized, everyone can contribute to it (without having to go through the package ownership process), and there is easy tooling to update and automate packages (See WingetCreate, Komac, and Winget Releaser). For non-package vendors, there also happens to be an external automation repo managed by the Winget Releaser author, which you can contribute to (https://github.com/vedantmgoyal2009/winget-manifests-manager).

I think this article summarizes the pain points of Chocolatey (From the AppGet author, which later became the inspiration for Winget): https://keivan.io/why-chocolatey-is-broken/