Here are the steps: (sample of .codepackager.yaml can be found in this project)
1. Put .codepackager.yaml into your home folder and configurate it with your setting.
The following directive can be ignored in this configuration file:
* "package-name" and
* "vcs"
This would be your local setting. You will need local setting in remote machine, too.
2. Put .codepackager.yaml into the root folder (where .hg or .git resides) of your repository.
Only "package-name" is required. This setting ("package-name") will use as packaged file name.
You can include other directives to customize for certain project if you really need it.
This would be your project/repository setting.
3. Add and commit the .codepackager.yaml in your repository.
4. Run "prep_codepkg.py" in root folder of repository to package the repository (and make backup).
5. Move mobile storage to remote machine.
Run "recv_codepkg.py /PATH/TO/PACKAGED_FILE" in repository folder of remote machine.
This step should bring configuration file to remote machine.
6. From now on, you can use "recv_codepkg.py" (without path of packaged file) to pull updates from mobile storage.
1 maintainer
Metadata
1 maintainer
Release files for codepackager 1.02
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 |
|---|---|---|---|---|
| codepackager-1.02.tar.gz | 8.2 kB | Without provenance | Details for codepackager-1.02.tar.gz |
Release files / codepackager-1.02.tar.gz
| Download URL | codepackager-1.02.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
246b00cefec73aabc4daf1080c879503f57b017933df84680f151667d6e41f3e
|
|
BLAKE2b-256 checksum How to use checksums |
fd2e46813732ad891ab06868c47bc1558fdad77e0fe96dd3e61becb9953090ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for codepackager 1.02
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.
