Closed
Bug 438824
Opened 17 years ago
Closed 15 years ago
Support for Solaris x86/SPARC
Categories
(addons.mozilla.org Graveyard :: Administration, enhancement, P5)
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: dbo, Unassigned)
References
Details
It would be really cool if AMO could support Solaris (both x86 and SPARC). At least the calendar project does releases for that platform regularly.
Comment 1•17 years ago
|
||
Justin, will bug 427098 fix this?
Comment 2•17 years ago
|
||
Justin, should this even just be a DUP of bug 427098?
Comment 3•16 years ago
|
||
duping to Bug 427098
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Updated•16 years ago
|
Component: Add-ons → Administration
QA Contact: add-ons → administration
Comment 4•16 years ago
|
||
This is not a dupe of bug 427098. That bug asked for the raise of the platform limit to more than three platforms.
Thus bug asks, that two separate Solaris platforms (x86 and SPARC) are added instead of just a general Solaris platform. For an extension like Lightning that ships binary components, we have to release one .xpi for each Solaris package.
The alternative would be to manually glue the two platform xpi files together (like a unified binary for the Mac), but that is a lot of pain and we would really like to avoid this in the future.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Updated•15 years ago
|
Priority: -- → P5
Target Milestone: --- → Future
Comment 5•15 years ago
|
||
Based on the current usage of platforms other than Windows, Mac, and Linux by add-ons on AMO, we'll actually be dropping BSD and Solaris in the upcoming Developer Tools revamp.
So we're not really interested in adding these additional platforms. If specific support for them is truly needed, I think those files won't be able to be hosted on AMO.
Status: REOPENED → RESOLVED
Closed: 16 years ago → 15 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•