[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mozilla-crypto
Subject:    Re: Status of PSM in Mozilla
From:       Chris Seawood <cls () seawood ! org>
Date:       2000-12-23 21:59:42
[Download RAW message or body]

Michael Kaply wrote:
> 

> 1. How did you fix the conflicts on the other machines - did you switch them
> to OBJDIR builds?

Most of the ports tinderboxes have been using a separate objtree for
months now.  Leaf cleared out the conflicts on the main tinderboxes by
removing those files and repulling.

> 2, Why are these stupid Makefiles checked in anyway when they can get
> created? 

Part of the psm landing was to switch from using the
SECURITY_CLIENT_BRANCH to using the psm tip.   While those Makefiles did
not exist on the branch, they do on the tip.  I cannot cvs remove them
because I have no idea if/how they are used in any other projects that
build psm.

> Why do we have another component that is as much of a nitemare as
> NSPR? On OS/2, we have had total success removing all the Makefiles in psm
> and nss and having them generated.

See http://bugzilla.mozilla.org/show_bug.cgi?id=60912 .  I didn't
realize that you weren't CC'd.  There was a lot of pressure on both
sides to get the changes landed but there was the usual classic/autoconf
build debate.  To avoid a prolonged deadlock and since the two psm
engineers were going to be on vacation/sabbatical for the next 2 weeks &
2 months respectively, it was decided to land the changes but to treat
PSM as an external module that's outside of the Mozilla build and to not
build it by default.   The long term plan is to move everything over to
using autoconf, at which point, psm/nss will be properly integrated into
the build system.

- cls

[prev in list] [next in list] [prev in thread] [next in thread]