This project has been archived by its maintainers, and is no longer receiving any updates.
livecheck
Tool for overlays to update ebuilds. Inspired by the MacPorts port subcommand of the same name.
Installation
On Gentoo, add my overlay and install:
eselect overlay enable tatsh-overlay
emerge --sync
emerge livecheck
Command line usage
Usage: livecheck [OPTIONS] [PACKAGE_NAMES]...
Options:
-a, --auto-update Rename and modify ebuilds.
-d, --debug Enable debug logging.
-e, --exclude TEXT Exclude package(s) from updates.
-W, --working-dir DIRECTORY Working directory. Should be a port tree root.
--help Show this message and exit.
Heuristic update detection
This package can do automated lookups based on commonly used hosts. Currently:
- GitHub archives
- GitHub commit hashes
- GitHub releases
- JetBrains products
- PyPI
This works as long as the version system is usable with Portage's version comparison function. For anything else, see Package configuration.
Package configuration
For packages that will not work with currently heuristic checking, a configuration file named
livecheck.json can be placed in the directory alongside the ebuild.
Configuration keys
type-none,regex, orchecksumbranch- The GitHub branch name to use for commitsno_auto_update- boolean - Do not allow auto-updating of this packageregex- The regular expression to usesemver- When set tofalse, do not allow detection of semantic versioningtransformation_function- string - Function to use to transform the version string. Currently onlydotizeis supported. Others are for internal use.url- URL of the document to run regular expressions againstuse_vercmp- boolean - ifvercmpfrom Portage should be used. Default:true.
Development use
Set up PYTHONPATH
As root, set the environment variable PYTHONPATH to include where the livecheck module is
located. Use python -m livecheck instead of livecheck to execute commands.
With a virtualenv
Run poetry install --all-extras --with=dev,docs,tests to set up a virtualenv.
Fully copy /etc/portage to the root of your virtualenv. Then you must fix make.profile. Also
consider making changes in repos.conf if necessary.
Example:
poetry shell
cd "${VIRTUAL_ENV}/etc"
cp -R /etc/portage .
cd portage
ln -sf "$(readlink -f /etc/portage/make.profile)" make.profile
Metadata
Release files for portage-livecheck 0.0.13
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 |
|---|---|---|---|---|
| portage_livecheck-0.0.13.tar.gz | 21.3 kB | Without provenance | Details for portage_livecheck-0.0.13.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| portage_livecheck-0.0.13-py3-none-any.whl | Python 3 | none | any | Details for portage_livecheck-0.0.13-py3-none-any.whl |
Total release size: 43.5 kB
Release files / portage_livecheck-0.0.13.tar.gz
| Download URL | portage_livecheck-0.0.13.tar.gz |
|---|---|
| Size | 21.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
871c8af0f699345f5f8f1f1edc8e7d6884090656651ae9fa316c6cb7a90f759c
|
|
BLAKE2b-256 checksum How to use checksums |
63fc534f7a80db385f00ef42d83764ce0642b66153f540fd966ca8d5f036f4b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.12.4 Linux/6.9.7-gentoo-limelight
|
Release files / portage_livecheck-0.0.13-py3-none-any.whl
| Download URL | portage_livecheck-0.0.13-py3-none-any.whl |
|---|---|
| Size | 22.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1eeb9fc5a288816c585da172f91bce2d932a5e3ab54fed515d828c77caa81530
|
|
BLAKE2b-256 checksum How to use checksums |
04900c53f428f230ceebc0d701c354878128b47fbb3cf578c890b74810866cb9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.12.4 Linux/6.9.7-gentoo-limelight
|
Security for portage-livecheck 0.0.13
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.