Merge lp://staging/~mrooney/ecryptfs/pythonapi into lp://staging/~ecryptfs/ecryptfs/ecryptfs-utils
Proposed by
Michael Rooney
Status: | Merged |
---|---|
Merged at revision: | not available |
Proposed branch: | lp://staging/~mrooney/ecryptfs/pythonapi |
Merge into: | lp://staging/~ecryptfs/ecryptfs/ecryptfs-utils |
Diff against target: | None lines |
To merge this branch: | bzr merge lp://staging/~mrooney/ecryptfs/pythonapi |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Dustin Kirkland | Approve | ||
Review via email: mp+6858@code.staging.launchpad.net |
To post a comment you must log in.
Dustin, this is the API branch and is ready to go. I created a new python/ directory in src/ which the UI utilities assume is shipped as a dist/site package of python named "ecryptfs" (for example as /usr/lib/ python2. 6/dist- packages/ ecryptfs/ )
The two things to resolve before packaging are: passphrase_ blob, ecryptfs_ passphrase_ sig_from_ blob, ecryptfs_ add_blob_ to_keyring) to ecryptapi.py and adjust any references.
- should it be somewhere different in the ecryptfs source?
- I'm expecting an 'ecryptfs' module to be added to dist-packages but 'ecryptfs-utils' already exists for the swig wrappers. They should perhaps be unified, and you can't import something with a dash in the name in python anyway so the existing module is suboptimal. If it isn't too invasive we might want to move the three methods (ecryptfs_