From: Stephan Mending <list@md5collisions.eu>
To: development@lists.ipfire.org
Subject: Re: Multimedia Libs
Date: Thu, 26 Mar 2020 10:47:22 +0100 [thread overview]
Message-ID: <0fa2c1ba-6e1d-9651-d7fd-3dda3febf38c@md5collisions.eu> (raw)
In-Reply-To: <564396BC-2941-49FE-AA2A-CA4ED0B72141@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1850 bytes --]
Thanks for clearence !
On 26/03/2020 10:10, Michael Tremer wrote:
> Hi,
>
>> On 26 Mar 2020, at 07:24, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>
>> Hi,
>>
>> On 25.03.2020 22:11, Stephan Mending wrote:
>>> I was wondering why IPFire needs codecs at all?
>> I'm wondering, too... ;-)
> There are a couple of reasons:
>
> The image libraries are used to generate graphs. There are multiple ways do encode those and there are plenty of interdependencies to it.
>
> The audio libraries are being used for libvirt, tshark to capture and decode audio and video, too.
>
> There are a couple of media streaming add-ons which also can re-encode things. It is of course up to everyone to decide if they want/need to use it.
>
>>> I bet there's a good reason. I just isn't clear to me.
>> As I see it, the main reasons are the ability to do it by Pakfire and -
>> perhaps - historical reasons(!?).
>>
>> The first things I noticed when I started with IPFire (~2011), were the
>> multimedia addons (see: https://wiki.ipfire.org/addons).
>>
>> Who in god's name *needs* (and *wants*) "jukebox features", a "server
>> for streaming MP3- and OGG-files" or "video recording" - plus more - on
>> a *firewall*!?
>>
>> I saw this and thought: "Ok then, this is a *bit* different from IPCop,
>> but what the heck. After all, you're not forced to install this cr** -
>> its in your own responsibility.
>>
>> If it were up to me, these addons could be removed completely.
>>
>> Let the discussion begin... ;-)
> I do not really want to re-open this one again. We dealt with that on repeat about 10 years ago.
>
> They are add-ons. There are plenty of others where I personally disagree with and yet they are in the distribution. People have different needs.
>
> -Michael
>
>> Jm2C!
>>
>> Best,
>> Matthias
next prev parent reply other threads:[~2020-03-26 9:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5C7D0AAC-730A-40BA-B398-8AED49A4867D@ipfire.org>
2020-03-25 20:55 ` Matthias Fischer
2020-03-25 21:11 ` Stephan Mending
2020-03-26 7:24 ` Matthias Fischer
2020-03-26 9:10 ` Michael Tremer
2020-03-26 9:30 ` Matthias Fischer
2020-03-28 4:54 ` Matthias Fischer
2020-03-28 7:41 ` Michael Tremer
2020-03-26 9:47 ` Stephan Mending [this message]
2020-03-30 5:08 ` Matthias Fischer
2020-03-30 5:17 ` Matthias Fischer
2020-03-30 9:10 ` Matthias Fischer
2020-03-30 9:31 ` Michael Tremer
2020-04-02 17:07 ` Matthias Fischer
2020-04-03 10:22 ` Michael Tremer
2020-05-23 10:08 ` Matthias Fischer
2020-05-25 9:29 ` Michael Tremer
2020-05-25 11:05 ` Matthias Fischer
2020-05-26 10:15 ` Michael Tremer
2020-05-26 17:13 ` Matthias Fischer
2020-05-28 11:54 ` Michael Tremer
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=0fa2c1ba-6e1d-9651-d7fd-3dda3febf38c@md5collisions.eu \
--to=list@md5collisions.eu \
--cc=development@lists.ipfire.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox