[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: a bug in default .mozconfig

From: Alexander Sack
Subject: Re: a bug in default .mozconfig
Date: Thu, 16 Aug 2007 14:52:33 +0200
User-agent: Mutt/1.5.13 (2006-08-11)

On Wed, Aug 15, 2007 at 06:21:30PM -0500, Karl Berry wrote:
> Hi Mike,
>     > http://lists.gnu.org/archive/html/bug-gnuzilla/2007-06/msg00002.html,
> I was under the impression that there was an eventual goal of having GNU
> iceweasel be the upstream for Debian iceweasel.  
> I know it hasn't happened yet.  If this doesn't seem likely to ever be
> the case, we should probably rename GNU iceweasel now to avoid this
> recurring confusion.  Wdyt?
> However, we hope you will actually want the privacy-related changes that
> Giuseppe described.  FYI, rms originally requested them, to give users
> more of a reason to use gnuzilla/iceweasel.
> As for the patches, if Gisueppe's message leaves anything unclear, can
> you say specifically which changes you want the rationale for?   There
> are a lot ...

>From what I remember the idea once was to move the gnu privacy/plugin
features to an extension which gnu iceweasel can ship by default. 

I did this for the plugin finder dialog once, but never got to
implement the privacy features in real, as Giu was not able to provide
me with a distinct patch of the privacy features only .... and finally
i droppped the ball on this.

Now, from what i perceived so far (note that i might be wrong because i
never could take a look at a minimal patch, so correct me when i am
wrong) is that the privacy features are not really reasonable (aka
broken from a technical pov) ... as they can be worked around
(javascript, css) and it will be nearly impossible to catch all cases
... which makes me think if its still worth the efford to maintain
those ...

anyway ... my offer still stands to help you move your features
cleanly to an extension that will help you to merge your changes into
the iceweasel source tree we distribute in debian while getting rid of
maintenance pain - aka keeping patches on top of a moving code base.

( BTW, we now have a ice-1.8 git branch where we track mozilla upstream
1.8 branch MINUS the binary/non-free files [1])

[1] ... http://git.debian.org/?p=pkg-mozilla/upstream.git;a=summary)

 - Alexander

reply via email to

[Prev in Thread] Current Thread [Next in Thread]