This release is a pre-release and may not be stable for production use.
infrae.subversion. all credits to the original author
A buildout recipe which can be used to branch a Bazaar repository.
This makes it possible to automatically create branches for relevant
code.
Usage
=====
If you have a buildout config you can add a section like:
[sources]
recipe = bazaarrecipeinfrae
urls =
http://bazaar-vcs.org/bzr/bzr.dev bzr.dev
http://bazaar.launchpad.net/~bialix/heads/trunk heads
This will create a `sources` folder in you buildout root with two
subfolders in it (bzr.dev and heads).
Changes to you buildout configuration might trigger removal of the
sources dir. However, before this happens the recipe makes sure there
are no modifications left. If it sees any it will abort before
anything is deleted. This means you can safely use it for development.
Running buildout again after you have done a succesful build before
will do a bzr pull on each of the resources.
1 maintainer
Metadata
1 maintainer
Release files for bazaarrecipeinfrae 0.1.2dev
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 |
|---|---|---|---|---|
| bazaarrecipeinfrae-0.1.2dev.tar.gz | 2.5 kB | Without provenance | Details for bazaarrecipeinfrae-0.1.2dev.tar.gz |
Release files / bazaarrecipeinfrae-0.1.2dev.tar.gz
| Download URL | bazaarrecipeinfrae-0.1.2dev.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f8294ad7b53b68fc7b3ee9de406b99d4d17623e803be0920f7ac015325a87ec1
|
|
BLAKE2b-256 checksum How to use checksums |
e8b926a9110117565a3c420f28840a25d51b68b5febaf66a22bf586696919ec5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for bazaarrecipeinfrae 0.1.2dev
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.
