-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nullsoft installers (or MSI) + winget #135
Comments
I don't really see how this could be sensibly put into an installer. |
Just drop everything into |
Just install to program files and update the PATH environment variable
…On Thu, Mar 10, 2022 at 5:46 PM garoto ***@***.***> wrote:
Just drop everything into C:\Windows and it should be fine.
—
Reply to this email directly, view it on GitHub
<#135 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGA4ZY6DYRSEA3GXIVYFU3U7KCU7ANCNFSM5QM7LVOQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I don't think an installer is a good idea as it gives the wrong idea to users about there being any sort of official location/build/path for ffmpeg. |
@DanTheMan827 and @garoto, most users are hesitant or unable to perform those operations, and @BtbN, standard paths for installation definitely exist: these are usually "file:///%SystemDrive%/Program%20Files" and, for user-specific files, %AppData%. I am unable to ascertain why the mere presence of the installer would demonstrate somehow that this is official, as is purported. If such designation is undesirable, I suggest that this location be removed from "https://ffmpeg.org/download.html#build-windows#:~:text=ready%20to%20go.-,windows%20exe%20files,-Windows%20builds%20from". The lack of an installer merely causes this to be unnecessarily difficult to install. |
@BEEDELLROKEJULIANLOCKHART @BtbN I wasn't suggesting anything because it was "official", but merely because winget as a package manager just makes it easier for people to re-install software after a format or just keep it up to date. There's a couple projects with multiple variants in winget maintained by different teams and they're just differentiated by their designation. BtbN.FFmpeg would be the one for this project if there were installers available, but that wouldn't make it the official ffmpeg, just this build of it. |
It would be very convenient if this could be packaged inside an installer and automatically submitted to the winget package repository at microsoft/winget-pkgs
I've found this post detailing how you can automatically submit to winget https://www.dolthub.com/blog/2021-10-13-how-to-publish-winget-chocolatey-packages-with-github-actions/
The text was updated successfully, but these errors were encountered: