Closed
Bug 139858
Opened 22 years ago
Closed 22 years ago
No talkback enabled (nightly) builds for Linux-PPC aviable
Categories
(Core Graveyard :: Talkback Client, defect)
Tracking
(Not tracked)
VERIFIED
WONTFIX
People
(Reporter: pab, Assigned: namachi)
Details
1) go to: http://ftp.mozilla.org/pub/mozilla/nightly/latest/
2) see yourself: no talkback enabled build for linux ppc is aviable
Ok, there are more Linux-x86 users than ppc users..
But since i'm running Linux on PPC only, it's impossible for me to send
Talkback-data..
I think for ppc, we don't need 2 builds, one with and one without talkback.. one
Build with talkback enabled would be good enough (users wich don't want to send
talkback data can turn it of..)
Comment 2•22 years ago
|
||
-> back to namachi, as per email discussion. I have nothing to do with LinuxPPC,
and it's not a supported platorm.
Assignee: jj → namachi
Reporter | ||
Comment 3•22 years ago
|
||
> and it's not a supported platorm.
..wontfix?
Assignee | ||
Comment 4•22 years ago
|
||
Talkback is not supported for LinuxPPC.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Reporter | ||
Comment 5•22 years ago
|
||
ok,
but a question: why?
are there licensing problems, no time (not enough potentiell users) or has the
talkback software problems with this plattform?
the software isn't there, there's no license for it, there's no market for it,
netscape isn't investing large gobs of anything into talkback and when it does
invest it's for large markets where netscape7+ and other commercial mozilla
derivatives are shipped (which currently does not include linuxppc)
note that releasing products with talkback isn't free, it requires a storage
investment for all of the symbols, especially if they're nightlies, but even if
you just keep symbols for all of the releases.
if you're interested in tracking down problems on LinuxPPC, build debug or
--enable-optimize="-O2 -g" --disable-debug, track down the problem as best you
can and file/find a bug.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•