[MPlayer-users] Re: feature request

[Stefan Seyfried]

"Sycotic Smith" <sycotic at linuxmail.org> writes:

> Are either feasible options, or both? Just brainstorming, maybe I need a braincoat?

I'm not very familiar with cpu specific coding, but i'm quite sure these
are moot point.

1. the detection does not really take a long time, i believe it is just
   some checking of /proc/cpuinfo
2. for binary installs, the problem is that you would need to pack different
   binaries for all different cpu types into the package and then only
   extract the one for the cpu you gave on the command line -> extremely
   high overhead. An alternative would be to provide different packages
   for every possible cpu. You are free to do that :-)

my opinion is, running mplayer on marginal machines (these are the ones where
cpu optimization really matters) is anyway a task for "advanced" users, since
there are other caveats to cope with. "Advanced" users should be able to
compile mplayer for themselves, and they will anyway because they always
want the latest and best goodies :-).
If someone is too dumb to compile mplayer, we can just tell him to buy a
faster system or get a clue :-))

regards,

    Stefan
-- 
 Stefan Seyfried, seife at gmane0305.slipkontur.de
+----------------------------------------------+

"If you want to travel around the world and be invited to speak at a lot of
 different places, just write a Unix operating system." -- [Linus Torvalds]