Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 2 Aug 2000 23:05:43 -0700
From:      Jeremy Lea <reg@FreeBSD.org>
To:        Maxim Sobolev <sobomax@FreeBSD.org>, "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc:        cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: ports/www/mozilla Makefile ports/www/mozilla/files md5 ports/www/mozilla/patches patch-ai ports/www/mozilla/pkg PLIST
Message-ID:  <20000802230543.F84140@shale.csir.co.za>
In-Reply-To: <3986FE1D.DB4F6C9@FreeBSD.org>; from sobomax@FreeBSD.org on Tue, Aug 01, 2000 at 07:43:10PM %2B0300
References:  <200008010630.XAA57708@freefall.freebsd.org> <20000801091824.E84140@shale.csir.co.za> <3986FE1D.DB4F6C9@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

On Tue, Aug 01, 2000 at 07:43:10PM +0300, Maxim Sobolev wrote:
> Oh, I'm terribly sorry. I tested this port on my 5-CURRENT system and
> it works for me. The reason I did the upgrade is galeon browser, which
> depends on Mozilla. However, if you wish I can backout this commit.

Firstly, several people have commented that they thought my reply was
rude.  I didn't intend it as such, only that I was unhappy.  I apologise
for being obviously over harsh.

However, (this is for Jordan) we have rules about maintainers, and although
it might be hypocitical of me to complain, since I've been known to tread on
people's toes before, I at least have managed to get mail off to the
maintainer, and wait out 24 hours.  We have the rules to keep the project
running smoothly, and if people ignore the rules, then I think they should
get a rap on the knuckles.

Back to the port.  The problem was not in the build.  It was crashing on
start up, because it was unable to initialise XPCOM.  I thought initially
that this might be a problem with libIDL, because I asked around to see if
any of the rules had changed, and people said no, but there were issues with
ORBIT-0.5.2.

Turns out the rules have changed.  The first person to run Mozilla must have
create permission in ${PREFIX}/lib/mozilla/components.  Obviously, people
reporting success are either running Mozilla as root, or installing it as a
user.

I'm going to commit a patch, but I'm also going to mark the port as
FORBIDDEN.  I was planning on doing this anyway when Mozilla reached beta,
since component.reg has to be writeable, and that's already a security hole
you can march an army through.  Having create permissions in a directory
full of auto loaded modules is just asking for trouble.

I'll have to sit down and figure out how to have per user component and
chrome files.  It shouldn't be a killer, but it's just going to take time I
don't have.

Regards,
 -Jeremy

-- 
FreeBSD - Because the best things in life are free...
                                           http://www.freebsd.org/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000802230543.F84140>