Make lazr-js use buildout and make it usable as an egg by other projects
Bug #446318 reported by
Björn Tillenius
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| LAZR Javascript Library |
Fix Released
|
Undecided
|
Björn Tillenius | ||
Bug Description
Lazr-js should use buildout to handle its dependencies. This will make it easer to add other depencies, such as cssutils.
When doing this, we should also make sure that it's possible to use setup.py to create a sdist of lazr-js, so that projects like Launchpad can create and use a lazr-js egg.
Related branches
lp:~bjornt/lazr-js/buildoutification
- Gary Poster (community): Approve
- Canonical Launchpad Engineering: Pending requested
-
Diff: 808 lines12 files modified.bzrignore (+9/-0)
MANIFEST.in (+5/-0)
Makefile (+27/-4)
README.txt (+14/-0)
bootstrap.py (+170/-0)
buildout.cfg (+32/-0)
ez_setup.py (+275/-0)
setup.py (+47/-0)
src-py/lazr/__init__.py (+8/-0)
src-py/lazr/js/build.py (+23/-11)
src-py/lazr/js/jslint.py (+2/-3)
src-py/lazr/js/scaffold.py (+2/-3)
| Changed in lazr-js: | |
| assignee: | nobody → Björn Tillenius (bjornt) |
| status: | New → In Progress |
| Changed in lazr-js: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
