Fernando Lopez-Lezcano <nando(a)ccrma.Stanford.EDU> writes:
On Thu, 2008-04-17 at 06:41 +0200, Jens M Andreasen
wrote:
On Wed, 2008-04-16 at 22:41 +0200, Mario Lang
wrote:
You are not really following what I am trying to
get across. Cross compilation
isn't the issue. The issue is that something as generic as i386 (or i686 for
rpm based distros IIRC) actually targets a lot of different types of hardware.
It can run on pretty old pentium based CPUs, but also modern
systems. A binary distributor has no way of knowing which
CPU is going to be used, ...
The distributor has one tool at his disposal, the package-manager. This
will know where it lives and could (potentially) choose the right
package.
The package manager does not choose the "right package". There is no
"right package". The packager does not know on which computer the
software will be running and can't pre-optimize for something that is an
unknown at compile or packaging time. The software has to automagically
optimize itself for the processor it is running on when it starts.
Well said.
That is the way this is done in many other audio
oriented software
packages (Jack, Ardour, etc).
+1
--
CYa,
⡍⠁⠗⠊⠕ | Debian Developer <URL:http://debian.org/>
.''`. | Get my public key via finger mlang(a)db.debian.org
: :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
`. `'
`- <URL:http://delysid.org/> <URL:http://www.staff.tugraz.at/mlang/>