Alvaro Martinez Echevarria wrote:
On Tue, 21 Nov 2006, Ari Pollak wrote:
On Tue, 2006-11-21 at 01:15 -0800, Alvaro Martinez Echevarria wrote:
The bug specifies that firefox does not work either.
Should that be confirmed before closing the bug?
Please accept my deepest apologies for missing a small parenthetical
remark in the subject of the message that wasn't mentioned anywhere in
the body of the actual report.
Sorry if I came off too harsh: but I still maintain that many
people may choose to use mozilla for a while, for whatever
reasons. I don't think support should be dropped yet.
On that note, what exactly happens when you try to use the plugin in
Firefox? Is it the same behavior as in Mozilla? Is the plugin listed if
you type "about:plugins" in the URL bar? What happens after you upgrade
to iceweasel?
I wouldn't know, as I didn't try it with firefox like the
original bug reporter. Maybe José Alburquerque can explain?
In any case, as of today, once iceweasel is installed,
things mostly work, with the exception of the divx plugins that
seem to have slipped through the cracks (unlike the other
plugins, the mplayerplug-in-dvx.* files are not linked from the
iceweasel directory on 3.31-5).
Regards,
I really only use mozilla for browsing, but on 11/14 when I updated to
version 3.31-3 of the mozilla-mplayer package, I noticed that the
plug-in was no longer available for mozilla so I tested it in with the
version of iceweasel (the latest) I was running at the time and it also
failed to work.
I later upgraded to version 3.31-4 and I noticed that it was still not
available for mozilla so I filed the bug and assumed that it was
persistent problem which also included iceweasel (I called it firefox in
the bug report).
When the maintainer so abruptly closed the bug, I really did not want to
argue so I decided that I would just "downgrade" to version 3.21-1 (in
testing) which did not present problems for me in mozilla. I figured
that once iceape/seamonkey was included in debian these problems would
be addressed and I would simply upgrade to iceape/seamonkey with no
problems whatsoever.
Before downgrading, I tested version 3.31-4 with iceweasel and noticed
that this version worked just fine with iceweasel so I decided to
simply ignore the closed bug report because I felt like mozilla was
being "marginalized". It didn't really make that much of a difference
to me because as I said, I downgraded to a version that worked just fine
with mozilla and think that when iceape is available for debian the
plug-in should work fine then.
In truth, I thought of asking if the plug-in would work with iceape in
the future, but I sort of figured that it would and really did not want
to make a big deal about the reasons that the developer gave for
removing support for mozilla.
My opinion is that if mozilla is available for other branches such as
unstable (sid), which I'm running, I don't think that mozilla support
should disappear. I don't understand if there is some licensing issue
(as I'm still new to the licensing problems that debian faces), so my
opinion is probably worthless, but I think that as long as mozilla is
available for unstable, support for mozilla should *not* be removed.
If however, this desire cannot be met, I would hope that the plug-in
will work with iceape (when available) in the future. In the meantime,
I'll stick with version 3.21-1 until all this is resolved.
Sorry if I sound a bit irate, it's just that it's frustrating when
support for something that's still available in the branch that I'm
using disappears because of some issue (licensing maybe?) that I simply
don't understand. I will however continue to make the best of the
situation as I really do like the way the debian paradigm is designed.
This is simply a minor "drawback" for me. Thanks.
--
Álvaro Martínez Echevarría <[EMAIL PROTECTED]>
``Pero yo que he sentido una vez en mis manos temblar
la alegría / ya no podré morir nunca. / Pero yo que he
tocado una vez las agudas agujas del pino / ya no podré
morir nunca''. [José Hierro, "El muerto"]
--
Sincerely
Jose Alburquerque
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
