From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [RFC] net-libs/xulrunner-1.9 slotting or not?
Date: Mon, 17 Mar 2008 11:33:45 +0100 [thread overview]
Message-ID: <47DE4909.4000804@gentoo.org> (raw)
In-Reply-To: <pan.2008.03.17.06.26.22@cox.net>
Duncan wrote:
> Unslotted xulrunner seems to be the consensus, so we aren't committing to
> "forever" maintain patches ourselves -- on a package-base that may well
> expand over time.
The consensus is to have updated applications, the new xulrunner seems
quite an improvement so make _quite_ sense move towards it.
> Some questions. What's the possibility of getting upstream to handle the
> renaming, thereby making slotting much easier while eliminating the
> "eternal" patch commitment? Has the issue even been brought up with
> mozilla-upstream? I know they aren't always the most receptive to
> community suggestions, but it's worth asking, anyway.
Discussing with upstream this would be good as well, BUT you shouldn't
rely on that.
> How many packages are we talking about?
A list had been produced already and is relatively short and some are
just nsplugins (and those shouldn't require a change)
lu
--
Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-03-17 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-15 16:12 [gentoo-dev] [RFC] net-libs/xulrunner-1.9 slotting or not? Raúl Porcel
2008-03-15 16:49 ` Alexis Ballier
2008-03-15 18:12 ` Rémi Cardona
2008-03-16 0:03 ` Donnie Berkholz
2008-03-16 6:30 ` Luca Barbato
2008-03-17 6:26 ` [gentoo-dev] " Duncan
2008-03-17 10:33 ` Luca Barbato [this message]
2008-03-17 10:52 ` Raúl Porcel
2008-03-20 12:43 ` [gentoo-dev] " Raúl Porcel
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=47DE4909.4000804@gentoo.org \
--to=lu_zero@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