> From [email protected] Thu Dec 18 19:54:06 2008 > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; > d=gmail.com; s=gamma; > h=domainkey-signature:received:received:message-id:date:from:to > :subject:mime-version:content-type:content-transfer-encoding > :content-disposition; > bh=YxPfS/0helBPmJXrW79/QTkJO7NwPwwAofUVQyCxJbo=; > b=aDp9s0CcA1jzjslyybkW19N5UXvOzll0eO8G/s3OEggPmOgBT5fdTrVTST2uUglf3j > lIJu/WAtVVvQYASOJKT1BEBQHm50lY7vDIcKbDYKaJjurs3jah49yXpHv7EIjDYpWxEj > cneV5iDZm5f2Y865sNvbcI0woKPUJZ4VyxNrc= > DomainKey-Signature: a=rsa-sha1; c=nofws; > d=gmail.com; s=gamma; > h=message-id:date:from:to:subject:mime-version:content-type > :content-transfer-encoding:content-disposition; > b=tdMJyHYvILNlHCxVtyqLgrrXL+CuYQoC3prurq1xTebh+Z9/CQcjpQtKygNPuKv+m2 > qfOAW7GgX5uQKXlbFxH3i5W5Njn9dvGoFW4QyWmUllj47Z1nVQodnad15jS+HBSi+MKu > +td1eflmLWAGgosDHbaFj7+IqgWKn+GDSFfxw= > From: Brynet <[email protected]> > To: [email protected] > Subject: Firefox 3.0.5 question.. > MIME-Version: 1.0 > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: 7bit > Content-Disposition: inline > X-Loop: [email protected] > Precedence: bulk > Sender: [email protected] > > Mozilla just recently released version 3.0.5, it fixes 4 things they deem > critical. > > I was just about to update my port as usual when I noticed that they bundle: > * nspr 4.7.1 (an older release, we use 4.7.3) > * nss 3.12.2 (an unreleased, "release" candidate) > > https://bugzilla.mozilla.org/show_bug.cgi?id=461082 > > How will it be updated? should Firefox even be using the nspr/nss ports?
So... What is your question? Should it use nspr/nss? Yes, because it's easier for me to maintain. The newer version of nspr 4.7.3 also fixes bugs that i wanted to be fixed. There are no interface changes for 4.7.1 <=> 4.7.3. Is there any real issue with that? Could you also provide patch? According to the bugzilla link you've provided Mozilla wants to ship firefox with nspr 4.7.3; however only talk happened...
