Introduction
This is a one line recipe to allow buildout users to refer to ${grp:GROUP} to obtain the current user’s UNIX group id. In other words, the results of:
$ id -g -n
on UNIX systems, for the user executing the buildout. This can be used with gocept.recipe.env to configure ownership of the buildout directory, e.g.:
$ chown -R ${env:USER}:${grp:GROUP} ${buildout:directory}
Changelog
1.1.0 (2012-04-09)
Clean up package [aclark]
1.0 (2011-02-17)
Clean up package
0.1 (2009-04-03)
Added basic functionality
Created recipe with ZopeSkel
1 maintainer
Metadata
1 maintainer
Release files for collective.recipe.grp 1.1.0
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 | |
|---|---|---|---|---|
| collective.recipe.grp-1.1.0.zip | 14.5 kB | Without provenance | Details |
Release files / collective.recipe.grp-1.1.0.zip
| Download URL | collective.recipe.grp-1.1.0.zip |
|---|---|
| Size | 14.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cc8611c1ecb36d28eb88560d030e97492f7ad141404c181702fa4c0f820a2fc7
|
|
BLAKE2b-256 checksum How to use checksums |
a6a00f7feefc9e004801d3b1e66ff530741b3d75361e7a1b6d5babe1d74b1b7c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.recipe.grp 1.1.0
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.
