I can't even remember the name of the package, but it has codecs and ffmpeg as part of its name. Now, _why_ was it removed alongside the chromium packages? It was unrelated to the browser package naming issue. I'm just curious to know whether it was a mistake or a decision based upon a certain resolution.
On Fri, Oct 30, 2009 at 4:32 PM, Ray Rashif <schivmeister@gmail.com> wrote:
I can't even remember the name of the package, but it has codecs and ffmpeg as part of its name.
Now, _why_ was it removed alongside the chromium packages? It was unrelated to the browser package naming issue.
I'm just curious to know whether it was a mistake or a decision based upon a certain resolution.
Ffmpeg codecs are included in the zip folder from googlebot. The ffmpeg PKGBUILDs where there, because the ppa build was split in many packages.
2009/10/31 Panos Filip <panosfilip@gmail.com>
On Fri, Oct 30, 2009 at 4:32 PM, Ray Rashif <schivmeister@gmail.com> wrote:
I can't even remember the name of the package, but it has codecs and ffmpeg as part of its name.
Now, _why_ was it removed alongside the chromium packages? It was unrelated to the browser package naming issue.
I'm just curious to know whether it was a mistake or a decision based upon a certain resolution.
Ffmpeg codecs are included in the zip folder from googlebot. The ffmpeg PKGBUILDs where there, because the ppa build was split in many packages.
That's better, thanks.
participants (2)
-
Panos Filip
-
Ray Rashif