gocept.cvs
zc.buildout recipe to checkout cvs modules, supporting tags and branches
Options
- cvsroot
The cvs root the modules you want to fetch are in (ending with a /)
- modules
modules you want to checkout (list of module;tag;destination)
- destination
destination directory for the checkouts (ending with a /)
Contributors
Roman Joost <rj at gocept dot com>
Michael Howitz <mh at gocept dot com>
Changelog
0.1.10
Verbosity of output now depends on verbosity set in buildout. Default is beeing not verbose.
0.1.9
Bugfix: The check for changes on uninstall no longer sets a sticky tag.
Bugfix: Uninstall now also stopps if there are added or deleted files which are not yet commited or conflicts.
Silenced update: No longer shows processed directory names.
0.1.8
Bugfixing: Nested checkouts don’t ‘inherit’ sticky tags from checkout ‘above’
0.1.7
Bugfixing: HEAD checkouts don’t have any sticky tags
0.1.5
support for specifying a path instead of a directory as destination for a single module
0.1.4
support for offline/newest buildout options
0.1
initial version
2 maintainers
Metadata
2 maintainers
Release files for gocept.cvs 0.1.10
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 |
|---|---|---|---|---|
| gocept.cvs-0.1.10.tar.gz | 7.0 kB | Without provenance | Details for gocept.cvs-0.1.10.tar.gz |
Release files / gocept.cvs-0.1.10.tar.gz
| Download URL | gocept.cvs-0.1.10.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
099aed072ba9393eebbaf352332859d1cd270b1af107a71198b41d37b0deff5e
|
|
BLAKE2b-256 checksum How to use checksums |
60b79de7d847cb0bf5b34c1db8e9426b3b3163763504e384d92913c3d629cbd6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for gocept.cvs 0.1.10
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.
