public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Raúl Porcel" <armin76@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:52:54 +0100	[thread overview]
Message-ID: <47DE4D86.4030604@gentoo.org> (raw)
In-Reply-To: <pan.2008.03.17.06.26.22@cox.net>

Duncan wrote:
> Luca Barbato <lu_zero@gentoo.org> posted 47DCBE68.5000109@gentoo.org,
> excerpted below, on  Sun, 16 Mar 2008 07:30:00 +0100:
> 
>> Raúl Porcel wrote:
>>> Xulrunner-1.9 is a big change, and the apps using it won't work until
>>> they are fixed. So this needs to be decided, i've been working on
>>> slotting xulrunner, and i'm ready to put it in the tree. However i'd
>>> like to see what developers(since they will be the ones who will have
>>> to deal with this) and users prefer. Even if an app is compatible with
>>> xulrunner-1.9, it will have to be patched if we slot xulrunner. Since
>>> the pkgconfig files for xulrunner-1.9 are renamed to avoid collisions
>>> with current xulrunner-1.8.
>>> The other approach would be not slotting it, p.mask xulrunner-1.9 and
>>> wait until all the packages work against it and then unmask.
>> Given the number of applications I'd rather have them fixed with the
>> patches pushed to respective upstreams if we got there first.
> 
> Thanks for the wisdom of asking about this, Raul.  Given the way you 
> worded things, it looks like the consensus is heading a way other than 
> you might have expected.
> 
> 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.
> 
> 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.
> 
> How many packages are we talking about?  Regardless of how we go, fixing 
> ten is going to be far easier than a hundred, or five hundred.
> 

Upstream won't do that...so i guess this means xulrunner gets unslotted :)
-- 
gentoo-dev@lists.gentoo.org mailing list



  parent reply	other threads:[~2008-03-17 10:52 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
2008-03-17 10:52     ` Raúl Porcel [this message]
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=47DE4D86.4030604@gentoo.org \
    --to=armin76@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