Merge lp:~tony-badwolf/quickly/quickly-extras into lp:quickly
Status: | Needs review | ||||
---|---|---|---|---|---|
Proposed branch: | lp:~tony-badwolf/quickly/quickly-extras | ||||
Merge into: | lp:quickly | ||||
Diff against target: |
134 lines (+51/-23) 3 files modified
data/templates/ubuntu-application/project_root/bin/project_name (+32/-8) data/templates/ubuntu-application/project_root/setup.py (+18/-2) data/templates/ubuntu-application/run.py (+1/-13) |
||||
To merge this branch: | bzr merge lp:~tony-badwolf/quickly/quickly-extras | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Michael Terry (community) | Needs Fixing | ||
Review via email: mp+106498@code.launchpad.net |
Description of the change
quickly package --extras does not set up paths and environment correctly and omits compiling schemas
This branch fixes paths and environment for working in /opt
Partially addresses bug 998910 quickly package --extras creates broken deb
and fixes related bug 976817 Compiling schemas not part of the application template
TODO: glib-compile-
Unmerged revisions
- 669. By Tony Byrne <email address hidden> <email address hidden>
-
bin/project_name cleaned with pylint and pep8
- 668. By Tony Byrne <email address hidden> <email address hidden>
-
merge from trunk
- 667. By Tony Byrne <email address hidden> <email address hidden>
-
quickly package --extras does not set up paths and environment correctly and omits compiling schemas
This branch fixes paths and environment for working in /optPartially addresses bug 998910 quickly package --extras creates broken deb
and fixes related bug 976817 Compiling schemas not part of the application templateTODO: glib-compile-
schemas needs to be called as part of quickly package --extras
but I don't know how to do that.
So I finally got around to looking at this! Sorry! This is a good code change. The one I put in for an SRU did a similar thing, but was too hacky to stay in.
The bin/project_name changes make sense, though you made a lot of not-strictly- necessary changes that will make it hard to 'quickly upgrade' existing setup.py's to match. It might be better to reduce your changes just to adding the DATADIR stuff.
In setup.py, you had good intent, but it's probably not a good idea to have setup.py look at debian/rules. setup.py is supposed to be independent and a lower conceptual level than debian/rules. I think it would be better to have bin/project_name to set DATADIR to an environment variable like QUICKLY_DATADIR or have the __python_ name_data_ directory_ _ variable be defined dynamically and duplicate some of the logic in bin/project_name.
In neither case does your branch have upgrade.py logic to match.
Our lives would be easier if we actually implemented the code we planned way back when we split the project_root up to override bin/ and python_lib/ contents at-will. I recall you were not thrilled with that plan back in the day. How do you feel these days?