Closed Bug 176382 Opened 22 years ago Closed 20 years ago

Request for xft enabled daily tarball builds

Categories

(SeaMonkey :: Build Config, enhancement)

x86
Linux
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: yusufg, Assigned: blizzard)

References

Details

Hi, Blizzard currently provides RPMS of xft enabled nightly builds at http://ftp.mozilla.org/pub/mozilla/nightly/experimental/xft I would appreciate if tarballs could also be provided for xft enabled nightly builds. This would allow one to keep multiple nightlies around for comparision Would also appreciate if the upcoming Mozilla 1.2 would provide an xft enabled mozilla with an installer
To blizzard, since he hopefully knows someone with a build setup that's capable of building those... Yusuf, in general builds get contributed by people... so your best bet is to find someone to contribute these builds.
Assignee: asa → blizzard
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** Bug 176410 has been marked as a duplicate of this bug. ***
Blocks: xft_tracking
Mozilla Nightly RH8.0 gcc3.2 Xft2/fontconfig tarball: http://www.hut.fi/u/tontti/mozilla/2002-10-27-15-trunk/
Due checkin of bug 239466 I cannot build new tarballs for Gtk1/Xft2/fontconfig, for now.
This bug is requesting xft enabled builds from mozilla.org. The question is, why does mozilla not provide such a build? They do it for Firefox - so what is the difference? Fact is that on many machines I tried, XFT-enabled builds look incredibly much better - or to put it differently, non-XFT enabled builds just look terrible in comparison to practically all other apps. See also bug 245997 where xft-enabled builds are requested for the releases.
Component: Browser-General → Build Config
QA Contact: asa → core.build-config
Resolving this bug, GTK2+XFT enabled nightlies have appeared in http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest/ just some days ago
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.