Closed Bug 264410 Opened 21 years ago Closed 13 years ago

freebsd ports patches integration tracking

Categories

(Core Graveyard :: Tracking, defect)

x86
FreeBSD
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: vlad, Unassigned)

References

Details

I was just pointed to a number of patches that the freebsd guys are maintaining for Firefox at http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/firefox/files/ -- most of the patches are to xpcom and nspr for freebsd support on various 64-bit platforms (alpha, amd64, ia64, sparc64). These should get reviewed and checked in to the tree, as appropriate.
See also http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/mozilla/files/ and http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/mozilla-devel/files/ which are "latest release" and "latest bleeding edge release" respectively (~ stable and trunk).
Can someone make sure those are reflected in Mozilla bugs? I'm afraid my brain is not big enough to track anything outside bugzilla these days, though I do cringe a little at asking people to do that given the history of these bugs and neglect, likely at my sucky hands. Requesting blanket aviary+ for freebsd ports changes, etc. etc.
Status: NEW → ASSIGNED
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0? → blocking-aviary1.0-
(In reply to comment #2) > Requesting blanket aviary+ for freebsd ports changes, etc. etc. I doubt this will make firefox 1.0; it's too close, plus there's nspr/xpcom changes that would need to be applied to aviary, 1.7, etc. Probably best to just do it on trunk and shoot for 1.1.
Blocks: 266981
Blocks: 266983
No longer blocks: 266983
No longer blocks: 266981
Depends on: 266981, 266983
Depends on: 275438
Mass abdication.
Assignee: shaver → nobody
Status: ASSIGNED → NEW
No activity for 7 years, closing
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.