From: Christopher Degawa via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>,
Christopher Degawa <ccom@randomderp.com>
Subject: [FFmpeg-devel] Re: [RFC] Microsoft store
Date: Tue, 11 Nov 2025 19:14:43 -0600
Message-ID: <CABDPGrzm3fYssZ1qXWBUjnHD7x4X_VegEU=ZKcAjDgC=WTs4dw@mail.gmail.com> (raw)
In-Reply-To: <aRPOAs2u91jAXdMm@neo>
On Tue, Nov 11, 2025 at 6:02 PM Michael Niedermayer via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
> Hi James
>
> On Tue, Nov 11, 2025 at 08:19:25PM -0300, James Almer via ffmpeg-devel
> wrote:
>
> > Do they serve applications that only run on the command line? Because
> they
> > surely are not talking about the libraries on their own, knowing their
> store
> > is not a package manager.
>
> They build a prototype page for us even. And that shows screenshoots
> of ffmpeg command line commands
I believe there is a precedent with Python and even Linux distributions
running under WSL, such as Ubuntu. As far as I recall, they install them
under "%LOCALAPPDATA%\Microsoft\WindowsApps" and prepend PATH with the
location. I recall seeing many online issues regarding running python.exe,
since Microsoft stubbed the binary there that just pulled up the Microsoft
Store page for python.
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-11-12 1:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 23:15 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-11-11 23:19 ` [FFmpeg-devel] " James Almer via ffmpeg-devel
2025-11-12 0:00 ` Michael Niedermayer via ffmpeg-devel
2025-11-12 1:14 ` Christopher Degawa via ffmpeg-devel [this message]
2025-11-12 4:32 ` Gyan Doshi via ffmpeg-devel
2025-11-13 5:29 ` compn via ffmpeg-devel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABDPGrzm3fYssZ1qXWBUjnHD7x4X_VegEU=ZKcAjDgC=WTs4dw@mail.gmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=ccom@randomderp.com \
--cc=michael@niedermayer.cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git