Since when did the 64-bit version of Ubuntu become the new free ubuntu
version?

1) I don't really see, why there should be differences in policies
regarding closed-source codecs between 368 and x64. Either remove it
from the 386 repositories (and loose about half of the users) or add it
to the amd64 (so the majority of the users that have 64-bits chips will
actually choose to run a 64-bit os)

2) Everybody that needs this (90% of all 64-bit ubuntu users?) is doing
this manually now on amd64 anyway. How is that more stable?

3) The technical details do not seem that complex, concerning we are all
doing this manually now ANYWAY. Are we are not the experts here.

In other words: the reasoning that is used to not do this, is both flawed and 
in conflict with the official policy.
There are currently four problems for the AMD64 desktop to become usuable 
without MANDATORY annoying tweaks by the end-user.
Two of these three have a good workaround, one does not, because the free 
solution keeps crashing. 

  1. There is no java-applet support. Blackdown used to work, but since
Feisty it has been crashing consistently when invoked. Yes, there are
bug-reports about this since Feisty. No developper involvement though.

  2.  Wine32. There are wine32 packages specially for 64-bit ubuntu
thanks to WineHQ. Maybe it's a good idea to just move those packages
into the standard repositories, since Ubuntu refuses to do the same, and
wineHQ is the official distrobutor of Wine. (i.e. its a trusted source).
Bugs have been filed about this since forever. No developper involvement
though.

 3. Flashplugin-support. The 64-bit repository does contain a
flashplugin-nonfree package, and it installs the 32-bit version of
flash. They just forgot to do nspluginwrapper. Bugs have been filed
about this since forever. No developper involvement though.

 4. Mplayer32/gstreamer0.10-pitfalldll . We don't need 32-bit mplayer or
32-bit gstreamer plugins, we just need them to work with 32-bit codecs.
Since totem-gstreamer is the default browser-plugin and video-player,
what we need is 32-bit pitfalldll. Shouldn't be too complicated. There
have been mplayer32 packages (and firefox32 packages) floating around
all over the internet. Estimated gues about a hundred. Yet zero in the
repositories. Are you intentionally blocking them?

 5. Popular games and applicaties that offer both source-code and 32-bit
binaries on their website are not in the repositories. Flock, Songbird,
Urban Terror, World of Padman. Current solution getdeb.net (why you
never made this guy a motu is beyond me, he packages more by himself
than half the repo's)

So, what's up with the systematic 64-bit sabotage?

-- 
The 64bit mplayer binary/package can't use the 32bit win32codecs to play *wmv 
files.
https://bugs.launchpad.net/bugs/571
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to