crxmake
Python script for building google chrome extension crx package. It is inspired by rubygems’ crxmake.
Ubuntu Installation
sudo apt-get install swig sudo pip install crxmake
Usage
# CLI
$ crxmake.py PACKAGE_BASE_DIR
# From python
>>> from crxmake import package
>>> package('examples/app', outfile='examples/release1')Example
An example extension named ‘app’ is provided in the examples/ directory for testing purposes:
$ crxmake.py examples/app
$ ls examples/app
$ app app.crx app.pemRequires
python 2
swig
M2Crypto (available via pip, requires swig)
“openssl” command: because current M2Crypto lacks func for rsa pubout DER
Legacy Dependencies
Appendix: m2crypto-0.20.2-enable-rsa-pubout.patch
“svn diff” output for appending the feature for rsa pubout DER.
Howto build m2crypto with it:
svn co http://svn.osafoundation.org/m2crypto/tags/0.20.2 m2crypto-0.20.2 cd m2crypto-0.20.2 patch -p0 < ../legacy/m2crypto-0.20.2-enable-rsa-pubout.patch python setup.py build
(I hope someone send it to M2Crypto maintainer ^^)
Resources
“M2Crypto”:http://chandlerproject.org/bin/view/Projects/MeTooCrypto
“crxmake”:http://github.com/Constellation/crxmake
“Packing Chrome extensions in Python”:http://grack.com/blog/2009/11/09/packing-chrome-extensions-in-python/
Release files for crxmake 0.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| crxmake-0.0.3.tar.gz | 3.6 kB | Without provenance | Details for crxmake-0.0.3.tar.gz |
Release files / crxmake-0.0.3.tar.gz
| Download URL | crxmake-0.0.3.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
90d9a970a72fe6062012a22caf87b918ea5c4f0be7a0dcf5c429fc70625c2ef2
|
|
BLAKE2b-256 checksum How to use checksums |
4f643298f4dc4d677f5adcbfe3d225aab1d8972fec4fab82b3052c9e679a5a1f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for crxmake 0.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
