From: Daniel D Jones <ddjones@riddlemaster.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Firefox
Date: Mon, 27 Jun 2011 19:52:08 -0400 [thread overview]
Message-ID: <201106271952.08864.ddjones@riddlemaster.org> (raw)
Can anyone explain why it takes so long for Firefox-bin to be unmasked?
That's not intended to be a rant or finger-pointing, but a serious question. I
can certainly understand the issues involved with ensuring that a complex
package compiles on various systems with all sorts of different drivers and
set-ups. But the -bin package is a precompiled binary that's merely
installed. It seems like it should be pretty simple and straightforward to
ensure that it works and unmask it.
Firefox just released 5.0 and announced that all development, including bug
fixes and security updates, had halted on 4.0. They plan to hold to similar
short-release cycles in the future. It's been four months since 4.0 was
released and it's still masked. If future releases see similar delays in
unmasking, Gentoo users will soon be two or three versions behind. We'll be
forced to either manually install, unmask the masked package, or run a
potentially buggy, insecure version. Any insight into the delay of unmasking
the binary verion that would help me understand the issue greatly appreciated.
--
"It seems to me that it is madder never to abandon one's self than often to be
infatuated; better to be wounded, a captive and a slave, than always to walk
in armor." - Margaret Fuller
next reply other threads:[~2011-06-27 23:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 23:52 Daniel D Jones [this message]
2011-06-28 0:44 ` [gentoo-user] Firefox Albert Hopkins
-- strict thread matches above, loose matches on Subject: below --
2006-02-04 13:09 Daniel D Jones
2006-02-04 13:26 ` Beau E. Cox
2006-02-04 14:09 ` Daniel D Jones
2006-02-04 16:37 ` Holly Bostick
2006-02-04 17:02 ` Daniel D Jones
2006-02-04 18:20 ` Chan Min Wai
2006-02-04 19:01 ` Holly Bostick
2006-02-04 13:30 ` Andrew Gaydenko
2006-02-04 13:32 ` Holly Bostick
2006-02-04 13:36 ` Scott Stoddard
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=201106271952.08864.ddjones@riddlemaster.org \
--to=ddjones@riddlemaster.org \
--cc=gentoo-user@lists.gentoo.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