From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Lastrite app-text/chmsee. Semi-lastrite libopensync-plugin-google-calendar.
Date: Mon, 30 Apr 2012 22:33:33 +0300 [thread overview]
Message-ID: <4F9EE90D.7030003@gentoo.org> (raw)
In-Reply-To: <1335814067.26630.3.camel@cathai>
On 04/30/2012 10:27 PM, Stelian Ionescu wrote:
> On Mon, 2012-04-30 at 22:00 +0300, Samuli Suominen wrote:
> [...]
>> The answer I got from Gentoo's Mozilla Team when I proposed bumping it
>> to latest from the Firefox tarball was that "use npapi-sdk or
>> spidermonkey instead".
>>
>> Some which have needed more than just npapi-sdk or spidermonkey have
>> happily migrated to gtkhtml, or webkit-gtk.
>>
>> So I don't think it really makes sense to package and **maintain**
>> something upstream doesn't support, therefore I'm agreeing with the
>> Gentoo's Mozilla Team decision on this.
>> So no xulrunner anymore, even if that means losing 'chmsee' and 'kiwix'.
>
> Upstream doesn't support it, but Debian, Fedora, openSuse and other
> distros do so the maintenance work would be shared
>
Debian, Fedora, and OpenSUSE as non-rolling distributions need to keep
Firefox up-to-date for security.
I suspect this is the main reason they have ended up rolling this type
of xulrunner package. (For backward compat.)
We don't really have that "problem", as we can stabilize things much
faster, and phase out xulrunner and it's consumers much faster.
next prev parent reply other threads:[~2012-04-30 19:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 6:21 [gentoo-dev] Lastrite app-text/chmsee. Semi-lastrite libopensync-plugin-google-calendar Samuli Suominen
2012-04-28 10:17 ` Michael Weber
2012-04-28 12:20 ` Ben
2012-04-28 14:15 ` Michał Górny
2012-04-29 10:54 ` Samuli Suominen
2012-04-29 11:42 ` Pacho Ramos
2012-04-30 19:00 ` Samuli Suominen
2012-04-30 19:27 ` Stelian Ionescu
2012-04-30 19:33 ` Samuli Suominen [this message]
2012-05-03 3:39 ` [gentoo-dev] " Ryan Hill
2012-05-03 20:53 ` Michael Weber
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=4F9EE90D.7030003@gentoo.org \
--to=ssuominen@gentoo.org \
--cc=gentoo-dev@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