276891 - Standalone NSPR-release out-of-date

Status: RESOLVED FIXED

(NSPR :: NSPR, defect)

Description

[Mikhail T.]

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.3; FreeBSD) (KHTML, like Gecko)
Build Identifier: 

The last release of NSPR (4.4.1) is hopelessly out of date with Mozilla  
software. Each project seems to have its own version instead contributing to  
the unfortunate "DLL hell" on the otherwise tidy systems.  
  
Packagers/porters (such as FreeBSD's ports team) are having a hard-time fixing  
this too, because some software (like Gaim and Evolution) needs only nspr, but  
Mozilla-based browsers expect to see an *unreleased* version of nspr and fail  
to build with the latest "official" release. 
 
Please, consider making an up-to-date NSPR release and removing the "bundled" 
NSPR from other trees to prevent such "forks" from happening again. 

Reproducible: Always



Expected Results:  
All NSPR-using software building and working happily with the latest official 
release of NetScape Portable Runtime.

Comment 1

[Wan-Teh Chang]

I am working on the NSPR 4.6 release.  Hopefully
it will be available soon.

Comment 2

[Wolfgang Rosenauer [:wolfiR]]

seems to be fixed now?

Comment 3

[Mikhail T.]

Unfortunately, there is still no source code posted on:  
http://ftp.mozilla.org/pub/mozilla.org/nspr/releases/v4.5.1/  
-- only Linux binaries (in violation of GPL :-)  
  
And, of course, no v4.6 of any kind... It's been over 6 months already :-( 

Comment 4

[Wan-Teh Chang]

Sorry about the delay.  The NSPR 4.6 source and binary
distributions are now available in
ftp://ftp.mozilla.org/pub/mozilla.org/nspr/releases/v4.6/.
In particular, the source tarball is
ftp://ftp.mozilla.org/pub/mozilla.org/nspr/releases/v4.6/src/nspr-4.6.tar.gz.

Comment 5

[Mikhail T.]

Thank you very much. All that's left now -- before this bug report can be 
closed -- is to prevail upon Firefox and Mozilla (anyone else?) projects to 
STOP bundling nspr with their own trees.  
  
Doing so will inevitable result in the same problem reoccuring in the future.  
  
Other parts of their respective trees should be shared as well (xpcom comes to  
mind first), but that's a much longer shot... Let's start with modularizing  
nspr properly... 

Comment 6

[Mikhail T.]

Who should this report be assigned to now? 

Comment 7

[Christophe Ravel]

The target milestone is already released. Resetting target milestone.