Closed
Bug 783070
Opened 12 years ago
Closed 12 years ago
Need to test building with local xulrunner
Categories
(addons.mozilla.org Graveyard :: Add-on Builder, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: canuckistani, Assigned: ochameau)
References
Details
bug 772681 has been resolved, making xulrunner available on celery machines. We need to test the ability to use xulrunner to package add-ons instead of the existing pythom implementation. Assigning to Alex for now, will need to coordinate next week with Alex & Piotr.
Assignee | ||
Comment 1•12 years ago
|
||
Piotr, can you give it a try ? You just need to use this SDK tarball: https://github.com/ochameau/addon-sdk/tarball/cfx.js and eventually add "--binary /path/to/xulrunner-bin" if it doesn't work out of the box. (python tries to automatically find xulrunner bin by itself but it may fail)
Comment 2•12 years ago
|
||
this isn't a full SDK is it? as I can't import it into the builder
Assignee | ||
Comment 3•12 years ago
|
||
It is a full SDK tarball, but it lacks of some release stuff like version number. It is like using github master. I can try to generate a fake release tarball if it can help?
Assignee | ||
Comment 4•12 years ago
|
||
So the only thing you have to do to have a correct version set is to modify /python-lib/cuddlefish/_version.py And replace at line 12: git_refnames = " (cfx.js)" by: git_refnames = " (HEAD, 1.10, origin/release, release)"
Comment 5•12 years ago
|
||
my git_refnames were different ... should I use a specific version of SDK? git_refnames = "$Format:%d$"
Assignee | ||
Comment 6•12 years ago
|
||
I don't know it is up to you to please builder code/scripts to accept this SDK test tarball. I have no idea what are builder expectations. What kind of issues are you having?
Comment 7•12 years ago
|
||
I believe there is no issue anymore ... Please reopen if in doubt
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•10 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
•